In exceptions.rakudoc, remove a CATCH keyword. Plus some stylistic improvements.
#4712
Conversation
This file contains hidden or 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
coke
reviewed
Nov 14, 2025
doc/Language/exceptions.rakudoc
Outdated
| for more information on this. | ||
|
|
||
| A C<try>-block is a normal block and as such treats its last statement | ||
| A C<try> block is a normal block and as such treats its last statement |
Collaborator
There was a problem hiding this comment.
As long as we’re in here: I think “and as such, uses its last statement as its return value.” reads better - if you agree, please add that update.
Collaborator
Author
There was a problem hiding this comment.
Oh yes, definitely.
schultzdavid
changed the title
CATCH keyword where all that matters is the blockCATCH keyword. Plus some stylistic improvements.
schultzdavid
changed the title
CATCH keyword. Plus some stylistic improvements.CATCH keyword. Plus some stylistic improvements.
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.
Since the outer
CATCHstatement serves no function here, I think the example will be more transparent without that keyword (i.e. with only{}instead ofCATCH {}).I guess one could try to cook something up with two nested
CATCHes that illustrates how the outerCATCHblock does give back control to the encompassing (main) block. However, as the example is now, neither of theCATCHblocks even gets entered in the first place, because no Failure is thrown in the main block. So removing theCATCHword before the outer block is an improvement.