d at domenic.me (2015-02-17T17:50:14.512Z)
Allen Wirfs-Brock wrote: > - `Function.prototype.toMethod` has gone away. Only class declarations and object literals can set a function's [[HomeObject]] I prefer to think of toMethod as "deferred", not "gone away" (taken to mean "for good" sometimes). ;-) > - `Object.prototype.toString` no longer censors use of legacy [[Class]] values. Yay! > - Fixed handling of throw and close methods received by a `yield*` (see bug https://bugs.ecmascript.org/show_bug.cgi?id=3526) (further refinements may still be coming). s/close methods/return methods/ I like calling it `close` still, too :-P. My inner Pythonista talking. > - Resolved bugs: 3723, 3721-3695, 3691-3688, 3686-3685, 3682-3680, 3678-3627, 3625-620, 3617-3608, 3606-3597, 3594-3581, 3579-3576, 3574, 3571-3563, 3561, 3558-3545, 3526, 3519, 3431, 3220, 3206 Great, looking forward to next draft and my red pen getting drained. Excelsior!
Allen Wirfs-Brock wrote: > > Changes include: > > * > Removed ‘new super()’ syntax > * > new.target meta-property no longer highlighted as tentative. > * > Methods defined within class definitions are now non-enumerable > * > Classes defined as class extends null {...} are now consider to be > derived classes > * > Constructors defined using class definition syntax throw when > called as functions > * > Function.prototype.toMethod has gone away. Only class declarations > and object literals can set a functions [[&&HomeObject]] > I prefer to think of toMethod as "deferred", not "gone away" (taken to mean "for good" sometimes). ;-) > * > Object.prototype.toSring no longer censors use of legacy %%lass > <http://wiki.ecmascript.org/doku.php?id=harmony:lass> values. > Yay! > * > Empty object destructuring patterns without default values (eg, { > }) throw if the value assigned to them is null or undefined. This > make { } more consistent with the behavior of [ ] > * > Array destructoring performs an InteratorClose upon iterators it > creates. > * > Fixed handling of throw and close methods received by a yield* > (see bug https://bugs.ecmascript.org/show_bug.cgi?id=3526 ) > (further refinements may still be coming). > s/close methods/return methods/ I like calling it `close` still, too :-P. My inner Pythonista talking. > * > IteratorClose no longer cares whether the object returned from the > ‘return’ method has done:true. > * > Resolved bugs: 3723, 3721-3695, 3691-3688, 3686-3685, 3682-3680, > 3678-3627, 3625-620, 3617-3608, 3606-3597, 3594-3581, 3579-3576, > 3574, 3571-3563, 3561, 3558-3545, 3526, 3519, 3431, 3220, 3206 > Great, looking forward to next draft and my red pen getting drained.Excelsior! /be