BUG: Fix Index.intersection returning same instance when indexes are equal GH#63169 #63179
+15
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes GH#63169.
Index.intersectionpreviously returned the original Index instancewhen both Index objects were equal and unique:
This caused identity issues when downstream code expected a new Index.
This PR ensures that a new Index object is always returned when
intersection is computed, even if both indexes are equal.
A new test has been added:
This confirms: