Re: When macros will get in, will the core get slimmed in favour of macro-definitions?

I doubt this will be possible in a backwards compatible manner. With ES6, we missed the opportunity to take more of a desugaring approach for new features. As a consequence, there now is a fair amount of micro variation between seemingly related features that is only describable in terms of

Re: When macros will get in, will the core get slimmed in favour of macro-definitions?

I think you will note that many of the built in methods in the spec are already implemented in JavaScript code in many implementations (v8, firefox). Similarly the ability to implement more fundamental features in terms of macro definitions may well be pursued by the implementations. But note

Re: When macros will get in, will the core get slimmed in favour of macro-definitions?

Sure, we'd want that. And sweet.js can handle a lot (it handled classes, destructuring, and other ES6 features before they were implemented in popular engines). This may take a while. Best way to ensure this outcome: more people learning, using, and helping improve sweet.js. /be

When macros will get in, will the core get slimmed in favour of macro-definitions?

Hello, in fact, I am just interested on the answer to the question placed in the subject, in the light of recent discussion emphasizing minimality. Thanks, Herby ___ es-discuss mailing list es-discuss@mozilla.org