Comment #7 on issue 4211 by [email protected]: Wrong precedence for arrow
function without parameters
https://code.google.com/p/v8/issues/detail?id=4211
Good point Andreas, there might be a chance here.
(a)(b) is a valid ConditionalExpression but is not a valid arrow function
formal parameter list. Perhaps we can make ConditionalExpression,
BinaryExpression, PostfixExpression, LeftHandSideExpression, and
MemberExpression all mark the production as an invalid arrow formal
parameter list if they detect an expression like (a)?(b):(c) or (a).b or
the like.
ParsePrimaryExpression *certainly* shouldn't consume arrow functions,
that's the origin of this bug. We need to move that to happen only in
ParseAssignmentExpression.
The approach to have ParseAssignmentExpression know more about parentheses
was also for the () and (...x) cases, to avoid ParsePrimaryExpression
returning *ok=true but an invalid expression. I was a bit scared of the
implications that might have.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" 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.
