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

[FEATURE] Returning multi values in lambda-expression must be explicit by [ret1, ..., retn] now #54

Closed
mu001999 opened this issue Feb 11, 2021 · 0 comments · Fixed by #55
Closed

[FEATURE] Returning multi values in lambda-expression must be explicit by [ret1, ..., retn] now #54

mu001999 opened this issue Feb 11, 2021 · 0 comments · Fixed by #55
Labels
feature redesign

Comments

@mu001999
Copy link
Collaborator

To avoid conflict when using lambda expressions as arguments
@mu001999 mu001999 changed the title [FEATURE] Allow implicit multi-return-value only when using return explicitly [FEATURE] Returning multi values in lambda-expression must be explicit by [ret1, ..., retn] now Feb 11, 2021
@mu001999 mu001999 mentioned this issue Feb 11, 2021
Merged
mu001999 added a commit that referenced this issue Feb 11, 2021
@mu001999
Merge #55: Update the parsing of lambda expressions and block
3f0c39b 
### Added

- Empty parameters can be omitted. For example, `@: 42;` is a lambda expression

### Changed

- Returning multi values in lambda-expression must be explicit by writing `[ret1, ..., retn]`, see [FEATURE#54](#54)

### Removed

- Disable using single statement as block by `, stmt`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature redesign
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update the parsing of lambda expressions and block
1 participant
@mu001999