A new ES6 draft, Rev28
From: Allen Wirfs-Brock <allen at wirfs-brock.com>
Removed own @@iterator properties from various standard iterators, they now inherit it from %IteratorPrototype%
I was rather confused about this in the spec. Thankfully, it's fixed.
Eliminated Symbol.create and @@create.
Where's the discussion?
On Tuesday, October 14, 2014, Isiah Meadows <impinball at gmail.com> wrote:
Where's the discussion?
rwaldron/tc39-notes/blob/master/es6/2014-09/sept-24.md
Enjoy ;)
Explains all. Thanks.
One other thing not mentioned is the difficulty in VM optimization for functions implementing that property.
One other thing not mentioned is the difficulty in VM optimization for functions implementing that property.
This is really vague - can you explain?
ES6 Draft 29, harmony:specification_drafts#october_14_2014_draft_rev_28
This is awesome : )
- Removed loader pipeline and Reflect.Loader API (functionality being transfered to sperate specification)
Any discussion about will author this separate spec - TC39?
- Updated default export syntax and semantics to support export of anonymous default functions
Interestingly, class expressions are not "HoistableDeclarations" which might result in the (somewhat) surprising behavior previously identified:
export default class C { }
let c = new C; // Error
On Oct 14, 2014, at 8:31 PM, Kevin Smith wrote:
This is awesome : )
thanks
Any discussion about will author this separate spec - TC39?
yes, same folks driving the work. Just decoupled the specs and schedules.
Interestingly, class expressions are not "HoistableDeclarations" which might result in the (somewhat) surprising behavior previously identified:
export default class C { } let c = new C; // Error
Hmm...I think you're right. Not clear why classes shouldn't be default exports, even though they aren't hoistable. Also, since an anonymous function can be exported as default I don't see why an anonymous class shouldn't also be acceptable.
Should be easy things to fix.
This is why we put drafts out for review!
thanks again,
On Tue, Oct 14, 2014 at 11:04 PM, Allen Wirfs-Brock <allen at wirfs-brock.com>
wrote:
This includes the major work items from the September TD39 meeting.
Changes include:
- Removed loader pipeline and Reflect.Loader API (functionality being transfered to sperate specification)
Any discussion about will author this separate spec - TC39?
yes, same folks driving the work. Just decoupled the specs and schedules.
I just tried to lookup some thing about modules on people.mozilla.org/~jorendorff/es6-draft.html. The Loader related stuff is now either unrecognizable or completely different. Why were such drastic changes made and where is the discussion about the path forward?
jjb
On Sun, Nov 2, 2014 at 2:07 PM, John Barton <johnjbarton at google.com> wrote:
On Tue, Oct 14, 2014 at 11:04 PM, Allen Wirfs-Brock <allen at wirfs-brock.com
wrote:
This includes the major work items from the September TD39 meeting.
Changes include:
- Removed loader pipeline and Reflect.Loader API (functionality being transfered to sperate specification)
Any discussion about will author this separate spec - TC39?
yes, same folks driving the work. Just decoupled the specs and schedules.
I just tried to lookup some thing about modules on people.mozilla.org/~jorendorff/es6-draft.html. The Loader related stuff is now either unrecognizable or completely different. Why were such drastic changes made and where is the discussion about the path forward?
Removed.
rwaldron/tc39-notes/blob/master/es6/2014-09/sept-25.md#loader
ES6 Draft 29, harmony:specification_drafts#october_14_2014_draft_rev_28
This includes the major work items from the September TC39 meeting.
Changes include:
There may be an end to this tunnel...