Use any Error
for caught error type of an exhaustive, non-throwing do..catch
#71129
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.
Prior to the introduction of typed throws, a
do..catch
always had a caught error type ofany Error
, even if there were no throwing sites within thedo
body. With typed throws, such ado..catch
would have a caught error type ofNever
, because it never throws. Unfortunately, this causes code like the following to produce an error, becauseNever
cannot be pattern-matched toHomeworkError.forgot
:For source-compatibility reasons, adjust the caught error type to
any Error
in this case, so we continue to accept the code above. Don't do this adjustment underFullTypedThrows
, because it's only there for compatibility.Fixes rdar://121526201.