parser incorrectly reports self type error for lambda in template
See original GitHub issueclass Test {
(x: Int) => x
}
sandbox/test.scala:2: error: not a legal self type clause (class dotty.tools.dotc.ast.untpd$Parens)
(x: Int) => x
^
sandbox/test.scala:2: error: package x is not a value
(x: Int) => x
^
sandbox/test.scala:2: error: package x is not a value
(x: Int) => x
^
three errors found
Issue Analytics
- State:
- Created 7 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
AWS error from Python: No module named lambda_function
Error was due to file name of the lambda function. While creating the lambda function it will ask for Lambda function handler.
Read more >Problem with OPTIONS requests · Issue #400 · aws/aws-sam-cli
The weird part is that if I try to access a different endpoint from the same template it executes the lambda function (as...
Read more >Resolve template validation or template format errors in ...
I receive an error message when I try to create my AWS CloudFormation ... For "Unrecognized parameter type: XXXXXXXX" or "Invalid template ......
Read more >How to report Node.js errors from AWS Lambda
js template to automatically monitor AWS Lambda functions for errors. In this post we'll teach you how to report errors from your own...
Read more >Read, Write and Parse JSON using Python - GeeksforGeeks
A Computer Science portal for geeks. It contains well written, well thought and well explained computer science and programming articles, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I see. So closures have to be put in parentheses by the REPL anyway.
@odersky Should we close this? The issue is fixed in the REPL