[JS-internals] Volunteers to investigate bug 720452? Intermittent Android jsreftest failure

2014-02-04 Thread Chris Peterson
Does anyone care to investigate this intermittent Android jsreftest failure? The bug is two years old, but still fails regularly. It's the 32nd most popular orange test this week (with 30 failures). Bug 720452 Intermittent Android jsreftest.html?test= | load failed: null http://brasstacks.mozi

Re: [JS-internals] Documenting long-term plans that aren't being directly/actively/specifically worked on

2014-02-04 Thread Brendan Eich
Jeff Walden wrote: So mostly ES6 gets rid of [[Class]] and splits it up into a mostly harmless @@toStringTag property, and individual customized hooks. ES7 may change again, and section numbers will change. Beware. The "de-nominalization" work is hard and ongoing. Allen has adapted ES6 classe

Re: [JS-internals] Documenting long-term plans that aren't being directly/actively/specifically worked on

2014-02-04 Thread Jeff Walden
On 2/3/14 10:37 PM, Chris Peterson wrote: Jeff, regarding proxies and JSClass, can you elaborate on "the idea of classes is in the middle of deprecation in ECMAScript"? In ES5 there's this thing called [[Class]] which in name is just a string ("Array" for arrays, "Object" for plain old objects

Re: [JS-internals] Documenting long-term plans that aren't being directly/actively/specifically worked on

2014-02-04 Thread Jeff Walden
On 2/4/14 7:02 AM, Boris Zbarsky wrote: On 2/4/14 1:37 AM, Chris Peterson wrote: Jeff, regarding proxies and JSClass Note that we're currently sort of moving in the opposite direction: we just gave proxies distinct JSClasses. The goal is to unify the two concepts into one, called "proxy", wh

Re: [JS-internals] Documenting long-term plans that aren't being directly/actively/specifically worked on

2014-02-04 Thread Boris Zbarsky
On 2/4/14 11:54 AM, Jason Orendorff wrote: Class::getProperty/setProperty etc. are stupid and we should be trying to kill them off. Yes, totally agreed. If you need that sort of stuff you should be using the proxy API or something similar, since that gets to the heart of shapes being useless

Re: [JS-internals] Documenting long-term plans that aren't being directly/actively/specifically worked on

2014-02-04 Thread Jason Orendorff
On 2/4/14 10:54 AM, Jason Orendorff wrote: > Jeff also makes or hints at some other, separable points. Shorter: Yes, we should be looking to eliminate (a) duplication between Class and ProxyHandler and (b) legacy Class features. -j ___ dev-tech-js-engin

Re: [JS-internals] Documenting long-term plans that aren't being directly/actively/specifically worked on

2014-02-04 Thread Jason Orendorff
On 2/4/14 9:02 AM, Boris Zbarsky wrote: > On 2/4/14 1:37 AM, Chris Peterson wrote: >> Jeff, regarding proxies and JSClass > > Note that we're currently sort of moving in the opposite direction: we > just gave proxies distinct JSClasses. Yeah, that’s the right direction. I won’t duplicate Boris’s r

Re: [JS-internals] Documenting long-term plans that aren't being directly/actively/specifically worked on

2014-02-04 Thread Boris Zbarsky
On 2/4/14 1:37 AM, Chris Peterson wrote: Jeff, regarding proxies and JSClass Note that we're currently sort of moving in the opposite direction: we just gave proxies distinct JSClasses. More importantly, currently "proxy" implies all sorts of behaviors lumped into one, starting with "no sha