@_pier @thejameskyle @domenic @sebmck JS is 20 years old. There are billions of trillions of lines of code with for/in loops.
-
-
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 -
Replying to @_pier
@_pier@thejameskyle@domenic@sebmck people didn't want concise literals and classes to have different semantics.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@thejameskyle@domenic@sebmck this IMHHHHO is the only valid point for this.2 replies 0 retweets 0 likes -
Replying to @_pier
@_pier@thejameskyle@domenic@sebmck fwiw I agree with the committee but my strong position was on concise methods on literals.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@thejameskyle@domenic@sebmck still not convinced. Is there an official statement on enumerability?2 replies 0 retweets 0 likes -
Replying to @_pier
@_pier@thejameskyle@domenic@sebmck you would make object literal methods non-enumerable? Or have an inconsistency?1 reply 0 retweets 0 likes -
Replying to @jamiebuilds
@thejameskyle@_pier@domenic@sebmck jQuery.mixin(obj, { foo: function() {} }) NEEDS to be same as mixin(obj, { foo () {} })2 replies 0 retweets 0 likes -
Replying to @wycats
@thejameskyle@_pier@domenic@sebmck and people wanted concise methods to have same enumerability rules in object literals and classes1 reply 0 retweets 0 likes
@thejameskyle @_pier @domenic @sebmck are you arguing for dropping that constraint? Or the first one?
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.