Waldemar Horwat wrote:
Which ES6 features can be backported into non-strict mode? (blank: no significant issues; ?: possible issues; x: semantics conflict with de facto web)? let (syntax issues) x const (divergent semantics) x function in block (divergent semantics) ? destructuring (syntactic conflict with array lookup) parameter default values rest parameters spread x tail calls (because of Function.caller) direct proxies simple maps and sets weak maps is / isnt (egal) iterators ? generators (interaction with scoping issues and yield keyword) generator expressions comprehensions private names quasi-literals pragmas (controversial) ? completion reform (Brendan: might be able to get away with it without breaking the web, but we don't know yet) x typeof null (Erik: It breaks the web) class super n/a modules methods in object literals <| ({[computed_name]: value}) (MarkM: what should happen with duplicate names in nonstrict mode?)
What about obj.{ ... } literal extension? It is not mentioned, and afaict is unproblematic, too.
Herby _______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
