Changed lambda literal syntax to be more concise (issue #1391) #1400
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR implements issue #1391 (RFC 24), changing the lambda syntax to be more concise, and more consistent with the "lambdatype" syntax, using curly braces as the bounds of the lambda.
Note that the implementation takes special care to give a convenient, comprehensible error message for the old lambda syntax, to try to make migration to the new syntax easier for people with existing codebases using the old syntax: