@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 coming to grips with enumerability meaning something concrete and unreformable is important imo1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@thejameskyle@domenic@sebmck Gosh, I’m so sorry I missed the conversation once it happened on the TC…3 replies 0 retweets 0 likes -
Replying to @_pier
@_pier@thejameskyle@domenic@sebmck JS is 20 years old. There are billions of trillions of lines of code with for/in loops.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats And all of them use hasOwnProp to be able to get straight to the state@thejameskyle@domenic@sebmck3 replies 0 retweets 0 likes
@_pier @thejameskyle @domenic @sebmck I am 100% opposed to making concise literals have non-enumerable methods; clear refactoring hazard.
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.