feat(ses): permit stage 3 float16 proposal API #2014
Merged
Conversation
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
kriskowal
approved these changes
Jan 27, 2024
erights
force-pushed
the
markm-permit-float16
branch
from
ca1b7d4 to
f1ebc22
Compare
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.
closes: #XXXX
refs: https://github.com/tc39/proposal-float16array
Description
We should continue to permit all safe API elements that have reached stage 3. This one is safe and had not yet been included.
Security Considerations
none
Scaling Considerations
none
Documentation Considerations
none
Testing Considerations
none
Compatibility Considerations
keeping up
Upgrade Considerations
none
Neither breaking, not warrants any mention in NEWS.md. As long as they don't see the warning, no one will care.
*BREAKING*:in the commit message with migration instructions for any breaking change.NEWS.mdfor user-facing changes.