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.

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

Wrap user-supplied code in immediately-invoked closure #248

Merged
merged 4 commits into from
Feb 15, 2021
Merged

Conversation

kevinmehall
Copy link
Owner

@kevinmehall kevinmehall commented Jan 18, 2021

Allow return and ? in the code block (#246), and prevent statements
like break/continue from messing up enclosing loops.

Allow `return` and `?` in the code block (#246), and prevent statements
like `break`/`continue` from messing up enclosing loops.
@kevinmehall kevinmehall marked this pull request as ready for review February 15, 2021 00:42
@kevinmehall kevinmehall merged commit 01440d0 into master Feb 15, 2021
@kevinmehall kevinmehall deleted the closure branch February 15, 2021 16:59
kevinmehall added a commit that referenced this pull request Jul 24, 2021
rust-peg wraps code blocks in immediately-invoked closures to control
the behavior of `return` and `?`. (related: #248)

Fixes #258
kevinmehall added a commit that referenced this pull request Jul 24, 2021
rust-peg wraps code blocks in immediately-invoked closures to control
the behavior of `return` and `?`. (related: #248)

Fixes #258
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant