Status: New
Owner: ----
New issue 1876 by [email protected]: const error reporting a bit off with
variable conflicts
http://code.google.com/p/v8/issues/detail?id=1876
Trying out the new harmony scoping in canary and noticed the error message
thrown when a const conflicts with a variable is a little off IMO.
eval("var a = 'a'; const a = 'a';");
Results in: TypeError: var 'a' has already been declared.
Would it not be more semantically correct for this to be more like:
TypeError: redeclaration of const 'a'
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
