Proposal static type constraints features

[Jordan Harband]

The default alternative is "neither" - I think something as fundamental as
type annotations would need to have intuitive and conflict-free syntax, and
absolutely would have a way to work cross-realm with both objects and
primitives, to both distinguish between them and to allow both (in the case
of primitives other than null/undefined).

On Sun, Jun 3, 2018 at 10:50 PM, YU HengChun <achun.shx at qq.com> wrote:

> Or enable both versions at the same time?
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180603/8c864e7b/attachment-0001.html>