Add test for difference between export * as x from and import * as x; export { x }
#4606
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 is a test for the difference described in tc39/ecma262#3710.
TL;DR
export { foo } from "mod"andimport { foo } from "mod"; export { foo }are equivalent: they both propagate the binding, so when both re-exported withexport * fromthey do not cause ambiguity.export * as foo from "mod"andimport * as foo from "mod"; export { foo }are not equivalent: the second one introduces a new binding, causing ambiguity. It would be unambiguous if both were doingexport * as foo from "mod". It's still be ambiguous (two bindings) if both were doingimport * as foo from "mod"; export { foo }The first commit just moves the tests related to binding ambiguity to a single folder, so that it's easier to tell what is already tested.