Comment #5 on issue 4211 by [email protected]: Wrong precedence for arrow
function without parameters
https://code.google.com/p/v8/issues/detail?id=4211
One idea that I discarded when originally implementing the parsing for
arrow functions is to build simultaneously the ASTs for both productions (a
parenthesized expression, and function parameter list), and choose among
them depending on whether the “=>” is found. At the time I discarded this
idea because of the additional memory usage, but I am just commenting it in
case it might be considered again, or that it can serve as inspiration on
other possible solutions.
(BTW, this idea is itself inspired by Parsec-style parsers as seen in
Haskell, when multiple parsers can match the same input — but of course
there it makes more sense because of the laziness of the language)
--
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.
