Normative: Don't coerce value if index is invalid in TypedArray [[Set]] #2332
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.
While all major engines currently perform value coercion for invalid indices, I believe it's not due to web-compatibility, but because of extensive test262 coverage.
Motivation
[[DefineOwnProperty]]
, which doesn't coerce[[Value]]
for invalid indices.[[Set]]
with receiver-altered one.[[Set]]
in different methods; this change will clean up non-index method a bit.Implementation prospect
Given that #1556 requires TypedArray's
[[Set]]
to be adjusted in V8 / SM / JSC, this change can be implemented along.