Ensure Object type in dynamic import() Runtime Semantics #108
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.
In the Runtime Semantics for the version of dynamic import() that takes an assertions argument, the second
argRef
and theassertionsObj
are not guaranteed to be Objects. e.g:But, Get() and EnumerableOwnPropertyNames both assert that the argument to them is an Object.
This change adds checks that these are of Type Object, and reject the promise with a TypeError if either is not.
assertionsObj
is still allowed to be undefined. This will be useful if we use the options bag for other things such as evaluator attributes, where a missingassertionsObj
shouldn't result in failure: