ES6 opt-in, reloaded

Allen Wirfs-Brock allen at
Mon Jan 16 18:00:15 PST 2012

On Jan 16, 2012, at 5:49 PM, David Herman wrote:

> On Jan 16, 2012, at 5:47 PM, Allen Wirfs-Brock wrote:
>> One of the thing that an "ES6" (or "extended code" as it is currently known in the ES6 draft) mode  that is distinct from "strict mode" does is allow us do add additional Early Errors that aren't in ES5 for various existing constructs.  It isn't clear that we could continue to have add these errors if we don't have this "mode" distinction as they are generally potentially breaking changes.
> The distinction still exists; it's just "code that is syntactically contained within a module."

Except that it isn't clear to me that such a syntactically scoped mode would be compatible with other goals expressed by others on this thread such as, for example, avoiding refactoring pitfalls.


More information about the es-discuss mailing list