Andreas, Oh, that's why! So glad it's a known issue you guys are working on. I hope for a fix since it's pretty confusing; the error popped up with let keyword said things of const keyword, but nothing from const. Would it be terrible to put up a warning when const keywords is spotted in non-strict mode?
Thanks, Don On Thursday, August 13, 2015 at 5:52:03 PM UTC+9, Andreas Rossberg wrote: > > You currently need to be in strict mode to get ES6 `const` semantics in > V8/Chrome. In sloppy mode, you still get the crazy legacy web semantics > that isn't block-scoped (similarly with function decls). We have shied away > from changing that so far, because we fear it might break the web (on > mobile in particular). We have added use counters to Chrome 44+ to get some > data about potential breakage. > > /Andreas > -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
