> Each new feature can be considered independently. Anything that is only > allowed within modules becomes a carrot to lead programmers to the improved > semantics, but whenever we can compatibly make something available to global > code, we should do so. No point needlessly depriving programmers of ES6 > goodies such as destructuring or spread/rest.
I’m not entirely sure, but introducing two new dialects (ES5.5 and ES6, if you will) at the same time seems problematic. It might be easier to stick to the simpler rule of “global = ES5”. Apart from that: sold. -- Dr. Axel Rauschmayer a...@rauschma.de home: rauschma.de twitter: twitter.com/rauschma blog: 2ality.com
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
