@wycats @brendaneich so if you later change class constructors to be callable in some way, could break code.
@getify @AdamRackis @BrendanEich ES5 constructors quite often throw when called, just in weird ways. What makes you think otherwise?
-
-
@wycats@adamrackis@brendaneich "what makes [me] think otherwise?" nothing more concrete than i've been around just as long as you. -
@getify@AdamRackis@BrendanEich you are making an empirical claim: ES5 constructors very rarely throw when [[Call]]ed. Self evidently false -
@getify@AdamRackis@BrendanEich http://this.foo = bar or http://this.foo in an ES5 strict constructor will throw 100%. -
@getify@AdamRackis@BrendanEich in a sloppy constructor http://this.foo = bar erroneously adds to the global object. -
@getify@AdamRackis@BrendanEich code that relied on blindly calling a constructor and it never throwing is broken in ES5, full stop -
@wycats@adamrackis@brendaneich nonsense. absolutes like that get us nowhere. -
@wycats@adamrackis@brendaneich you'll notice my example code didn't rely on that. it used .call to provide a substitute context. -
@getify@AdamRackis@BrendanEich your notion of compatibility does not match mine. Let's agree to disagree. - 1 more reply
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.