At runtime they'd be similar to awaiting an import statement.
Maybe a requirement should be that nested (statically-analyzable)
imports should appear only within async functions (so they operate
the same as await import()).
Is there something bad about the idea that isn't described in those writings?
#!/JoePea
Why isn't it a thing yet?
- http://www.petecorey.com/blog/2016/07/17/meteors-nested-import-controversy/
- https://github.com/benjamn/reify/blob/master/WHY_NEST_IMPORTS.md
At runtime they'd be similar to `await`ing an `import` statement.
Maybe a requirement should be that nested (statically-analyzable)
imports should appear only within `async` functions (so they operate
the same as `await import()`).
Is there something bad about the idea that isn't described in those writings?
#!/JoePea
Why isn't it a thing yet?
At runtime they'd be similar to
awaiting animportstatement.Maybe a requirement should be that nested (statically-analyzable) imports should appear only within
asyncfunctions (so they operate the same asawait import()).Is there something bad about the idea that isn't described in those writings?
#!/JoePea