Make ns.foo
trigger evaluation also for non-existing properties
#33
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 change solves a few problem:
import defer * as ns
, but the solution in this PR also has the benefit in (2).import defer *
in tool, it's not always easy to know the list of bindings exported by a module at runtime without evaluating it. Examples are Webpack and Babel, that get the list of exports from properties of an object populated by the module evaluation. It would be possible in some cases to hard-code the list of exports, but it introduces additional complexity and duplicated information in the generated bundle.Symbols still do not trigger evaluation, because:
a. it's guaranteed that exports of a module have string names
b.
module[Symbol.toStringTag] === "Module"
can still be used to detect probable namespace objects without forcing their evaluation.