> To clarify, I was basically proposing exposing both the MNSEO with all
export members (like * as foo) as well as live bindings from the module,
separately. Something along the lines of a combination of the two.

Though I agree it would be nice to be able to do that in a single
statement, too, I’d imagine that adding it would take the form along the
lines of introducing `NamedImports , NameSpaceImport` or its inverse to
`ImportClause` — e.g.

    import { foo, bar }, * as baz from 'qux';

That is, there’s already syntax for both, they’re just not currently
permitted in a single statement — whereas what’s proposed here (`{} as`) is
a construction that doesn’t currently exist for a type of import that
doesn’t currently exist.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20171215/00650059/attachment.html>

> To clarify, I was basically proposing exposing both the MNSEO with all
> export members (like * as foo) as well as live bindings from the module,
> separately. Something along the lines of a combination of the two.

Though I agree it would be nice to be able to do that in a single
statement, too, I’d imagine that adding it would take a form along the
lines of introducing `NamedImports , NameSpaceImport` or its inverse to
`ImportClause` — e.g.

    import { foo, bar }, * as baz from 'qux';

That is, there’s already syntax for both, they’re just not currently
permitted in a single statement — whereas what’s proposed here (`{} as`) is
a construction that doesn’t currently exist for a type of import that
doesn’t currently exist.