@wycats: ES6 enumerable class methods. Why did this slip into the spec? /cc @domenic @sebmck @thejameskyle
@_pier @thejameskyle @domenic @sebmck it's heavily used today for coarse copying and comparing; $.mixin must work w/ upgraded classes
-
-
@wycats@thejameskyle@domenic@sebmck “Copying” doesn’t mean ‘have a interchangeable clone’, but ‘copy the **state**’ IMHO -
@_pier@thejameskyle@domenic@sebmck coming to grips with enumerability meaning something concrete and unreformable is important imo -
@wycats@thejameskyle@domenic@sebmck Gosh, I’m so sorry I missed the conversation once it happened on the TC… -
@_pier@thejameskyle@domenic@sebmck JS is 20 years old. There are billions of trillions of lines of code with for/in loops. -
@wycats And all of them use hasOwnProp to be able to get straight to the state@thejameskyle@domenic@sebmck -
@_pier@thejameskyle@domenic@sebmck people didn't want concise literals and classes to have different semantics. -
@wycats@thejameskyle@domenic@sebmck this IMHHHHO is the only valid point for this. -
@_pier@thejameskyle@domenic@sebmck fwiw I agree with the committee but my strong position was on concise methods on literals. - 6 more replies
New conversation -
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.