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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@crayxt : Thanks for patching this! Seems though that there might be bigger questions beyond just a simple typo fix (for better or worse) 😄
Though FYI, given how trivial the change is, you can also add
[ci skip]
to messages of commits like these to avoid triggering builds that should most certainly pass.@jreback : Is there any reason that this is implemented (not required from super-class)?
I don't see it used anywhere by
IntIndex
, and the implementation is justpass
even though the documentation (grammar error notwithstanding) says it should do something.If it is supposed to be used, should we move this method to the
SparseIndex
class (common method among the two sub-classes in that file)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah looks like was for a possible impl. Certainly could refactor if you'd like.