Support for general slicing #17
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR will track adding support for general slicing behavior (i.e.
mat[:5,:42,:]. As far as I can see, each such slice should create a clonesparsestackinstance, which gets filled in with appropriate values.This PR will not include general slicing assignment though, so no
mat[:1,:2]=42kind of behavior for now.I think this also kinda addresses the matchms/matchms#383
Still work-in-progress. Need comments on the likely breaking changes too (i.e.
mat[:,:]now returns a second instance ofsparsestack, not a tuple ofr,c,d).