Re: GGC (generational garbage collection) has landed for B2G

2014-09-17 Thread Gabriele Svelto
Having previously worked on a couple of GCs I must say this is amazing work! I don't know many other large, complex code bases such as Gecko that were moved successfully from a conservative mark-and-sweep collector to an accurate generational one. Bravo to everyone involved! Gabriele On 16/09/20

Re: GGC (generational garbage collection) has landed for B2G

2014-09-17 Thread Terrence Cole
On 09/16/2014 02:34 PM, Asa Dotzler wrote: > On 9/16/14, 12:45 PM, Steve Fink wrote: >> GGC was enabled yesterday (2014-Sep-15) on b2g-inbound with bug 1020751. >> It has not yet been merged into mozilla-central, but I expect it will be >> soon. GGC is already on desktop Firefox, and in fact just s

Web APIs documentation meeting Friday

2014-09-17 Thread Eric Shepherd
The Web APIs documentation meeting is Friday at 10 AM Pacific Time (see http://bit.ly/APIdocsMDN for your time zone). Everyone's welcome to attend; if you're interested in ensuring that all Web APIs are properly documented, we'd love your input. We have an agenda, as well as details on how to

Re: ES6 lexical temporal dead zone has landed on central

2014-09-17 Thread Chris Peterson
On 9/15/14 4:43 PM, Shu-yu Guo wrote: If you work with JS that contains `let` bindings, you may start encountering the following two errors: 1. TypeError: redeclaration of variable foo To fix, rename the variable or remove the extra `let` if you are assigning to an already-bound

Re: ES6 lexical temporal dead zone has landed on central

2014-09-17 Thread Shu-yu Guo
Well, SM's 'let' extension never really let you redeclare let bindings. What happened was that it was too much work to parse function body-level lets as actual lets, and so they were parsed as vars, thus allowing "redeclarations". Keep in mind that vars aren't *really* redeclared. When actual se

Re: ES6 lexical temporal dead zone has landed on central

2014-09-17 Thread Bill McCloskey
If this change proves to be really disruptive to add-on authors, I wonder if we could just make "let" behave like "var" for add-ons? The JS tokenizer could just substitute var for let when parsing code from an add-on compartment. (Bug 1030420 will put add-on code in a separate compartment and it