Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add support for new anonymous function syntax #142

Open
lucaswerkmeister opened this issue Sep 10, 2017 · 0 comments
Open

Add support for new anonymous function syntax #142

lucaswerkmeister opened this issue Sep 10, 2017 · 0 comments
Labels
feature
Milestone
Next release

Comments

@lucaswerkmeister
Copy link
Member

See eclipse-archived/ceylon#7190.
@lucaswerkmeister lucaswerkmeister added this to the Next release milestone Nov 19, 2017
lucaswerkmeister added a commit that referenced this issue Sep 17, 2018
@lucaswerkmeister
Switch parsing order in parseAnySpecifier
7becbab 
Since eclipse-archived/ceylon#7190, an expression like `=>a*b+c` is valid: it is
a function expression with zero parameter lists (see also #142). And
apparently the parser will parse it as such when asked to parse this
code as a (non-lazy) specifier (though I’m not sure why), whereas we
actually want this to be parsed as a lazy specifier in this context. We
can avoid this by attempting the lazy specifier parse first and falling
back to the non-lazy case second. (Even better would be to only call the
parser once, but there’s no direct rule for “any specifier”, and I’m not
convinced that the alternative – turning the code into a complete
example for some other rule, e. g. typedMethodOrAttributeDeclaration –
would be better.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature
Projects
None yet
Milestone
Next release
Development

No branches or pull requests
1 participant
@lucaswerkmeister