document running no "syntax checks for block exits" (added first in MRI 3.3.0) #975
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…RI 3.3.0) This commit tracks upstream commit ruby/ruby@e1250a5.
iliabylich
deleted the
document-running-no-syntax-check-for-block-exits
branch
This was referenced Dec 28, 2023
Closed
Closed
Closed
Closed
Closed
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commit tracks upstream commit ruby/ruby@e1250a5.
This MRI change is an evil twin of "void value expression" checks. If you want to give it a try feel free to send PR. I'm not the one designing Ruby but IMO it should be a runtime check.
This PR simply admits and documents incompatibility with MRI.
Closes #940