Use Float16Array for to/fromHalf utilities if supported
#161
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
Contributor
|
Thank you! |
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.
Similar to what is done for
floatBitsToUint/uintBitsToFloatthetoHalf/fromHalfcan be implemented using aFloat16ArrayandUint16Arraypair. Since support forFloat16Arrayis relatively new (https://caniuse.com/mdn-javascript_builtins_float16array) this PR checks if it's present, otherwise falling back to the current JS implementation.There's a performance uplift with this approach. Though since the
toHalf/fromHalfis only used for encoding and decoding the center of splats, it's overall impact on parsing time is limited.