[SILGen] Output a different message for failed IUO force-unwraps #17826
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.
Modifies SILGen and the
Swift._diagnoseUnexpectedNilOptional
call to print a slightly different message for force unwraps which were implicitly inserted by the compiler for IUOs. That is, these two lines will produce different messages:The message is chosen based on the presence of certain flags in the
ForceValueExpr
, not on the type of the value being unwrapped, somyIUO!.foo()
would print the first message, not the second.Resolves SR-8170.