RFC: typed array conveniences #47
Open
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
kjvalencik
reviewed
Jul 25, 2022
Member
kjvalencik
left a comment
kjvalencik
left a comment
There was a problem hiding this comment.
This design looks really great! I'm exited for the flexibility this provides.
I left some of my thoughts.
- len()/offset()/size() instead of len()/byte_offset()/byte_length() - Handle::region() and Region::to_typed_array() take &self - to_region() -> region() - add JsArrayBuffer::region() convenience for docs purposes - neon::types::binary -> neon::types::buffer - document the alternative idea of compositional regions and why we didn't choose it
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 RFC defines a number of missing convenience APIs for typed arrays: constructors and metadata queries.
Implementation: neon-bindings/neon#909
Rendered