Add coverage for abrupt completion from ToNumber via ToUint16 in String.fromCharCode #4804
+53
−0
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 PR adds coverage for the case where ToUint16 produces an abrupt completion because its initial ToNumber step throws. (ToUint16 step 1)
String.fromCharCode converts each argument with ToUint16, and ToUint16 begins by applying ToNumber. So if the argument triggers an abrupt completion during ToNumber, that abrupt completion must be observable at the String.fromCharCode call site.
String.fromCharCode is a representative builtin that exercises ToUint16, so String.fromCharCode(0n) is a straightforward way to cover this path: ToNumber(0n) throws, and the builtin must propagate that error.
More generally, should test262 aim to add similar coverage for other observable abrupt-completion paths that currently aren’t covered? Or is there a consensus in test262 to keep this kind of coverage limited to a few representative cases?