@wycats: ES6 enumerable class methods. Why did this slip into the spec? /cc @domenic @sebmck @thejameskyle
-
-
Replying to @_pier
@_pier Forward-refactoring: concise object literals need consistency with long-form, class w/ literals@domenic@sebmck@thejameskyle2 replies 0 retweets 1 like -
Replying to @jamiebuilds
@thejameskyle Yet it deviates from **actual** hosted/native classes…@wycats@domenic@sebmck5 replies 0 retweets 0 likes -
Replying to @_pier
@_pier@thejameskyle@domenic@sebmck it's heavily used today for coarse copying and comparing; $.mixin must work w/ upgraded classes1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@thejameskyle@domenic@sebmck “Copying” doesn’t mean ‘have a interchangeable clone’, but ‘copy the **state**’ IMHO5 replies 0 retweets 0 likes -
Replying to @_pier
@_pier@thejameskyle@domenic@sebmck for(let prop of better(obj)) will let us evolve a better model on top of the new reflection API1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats BTW we still don’t have a stable foreach, with keys **and** values…@thejameskyle@domenic@sebmck1 reply 0 retweets 0 likes
@_pier @thejameskyle @domenic @sebmck it's trivial to write one with the new reflection APIs and for/of and we should do that in libs!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.