You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prefix: we are strongly considering to make import reflection an instance reflection instead of source reflection, like discussed at the November 2022 TC39 meeting. This issue assumes this change has happened.
There is a very fortunate interaction between the import ... from <ident> syntax this proposal introduces, and import reflection. It would allow users to ergonomically import and re-export whole entire module namespaces - a need that is currently very obvious from Deno's deps.ts convention.
Essentially, Module instances created by import module could be statically known and traced, just like module declarations. As such it should be possible to import from these modules with the import ... from <ident>; syntax.
The text was updated successfully, but these errors were encountered:
Prefix: we are strongly considering to make import reflection an instance reflection instead of source reflection, like discussed at the November 2022 TC39 meeting. This issue assumes this change has happened.
There is a very fortunate interaction between the
import ... from <ident>
syntax this proposal introduces, and import reflection. It would allow users to ergonomically import and re-export whole entire module namespaces - a need that is currently very obvious from Deno'sdeps.ts
convention.Example:
Essentially,
Module
instances created byimport module
could be statically known and traced, just like module declarations. As such it should be possible to import from these modules with theimport ... from <ident>;
syntax.The text was updated successfully, but these errors were encountered: