Normative: DataView methods should throw for absent byteOffset #604
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.
ES2016's GetViewValue (and the SetViewValue) throws for undefined byteOffset arg, after #410, it casts to 0 using ToIndex
This change throws a TypeError only when the argument is absent. e.g.:
new DataView(buffer, 0).getFloat32()
The alternative for this change is changing GetViewValue and SetViewValue, but that would also affect when the argument is present as
undefined
and the methods would become slightly different from the normalization introduced with ToIndex.