-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clib.Session.virtualfile_from_vectors: Now takes a sequence of vectors as its single argument (Passing multiple arguments will be unsupported in v0.16.0) #3522
Merged
Merged
Changes from all commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
29bd3f8
**Breaking**: clib.Session.virtualfile_from_vectors now takes only on…
seisman f5b0e8e
Backward compatible with the old way
seisman 361d837
Merge branch 'main' into refactor/virtualfile_from_vectors
seisman f786b8e
Add type hints and format docstrings
seisman 3893211
Further improve the docstrings
seisman b7b87c6
Separate message strings
seisman 6481df2
Reformat error message and remove the case '_' statement
seisman 089ef3f
Fix a typo
seisman 1a43e38
Fix typos
seisman 697d66b
Merge branch 'main' into refactor/virtualfile_from_vectors
seisman 7ef4e01
Merge branch 'main' into refactor/virtualfile_from_vectors
seisman b2032c8
Merge branch 'main' into refactor/virtualfile_from_vectors
seisman c41806e
Merge branch 'main' into refactor/virtualfile_from_vectors
seisman 61f323c
Fix [skip ci]
seisman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
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.
Maybe just put
_data = data
in thecase _
below? I'd actually prefer if we make it more explicit like:So that if there's a new
kind
in the future, we know to add it explicitly.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.
We can't do it like this, because we're currently writing case statements like
case "image" if data.dtype != "uint8":
, which only catches the case whenkind="image"
anddata.dtype != "uint8"
.We can refactor the codes to:
or
I still prefer the current codes, which set
_data
todata
by default and the match-case statements only need to deal with exceptions.If there is a new
kind
in the future,_data=data
is still the default. If needs special handling and we forget to add it, then the related tests will fail anyway.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.
Ah ok, that makes sense, let's keep
_data = data
at the top then.