_isOptional(type(of:)) Does Not Do What You Think It Does #28994
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.
In particular, if value is
Any
in a generic context, thentype(of: value)
isAny.Protocol
which is never considered optional. As a result, the first clause here (that provided special handling for printing optionals) was never actually being used forprint()
or other similar paths. (Curiously, it was used for string interpolation.)Fortunately?
print()
was producing the right results for optionals because of a dynamic cast bug that failed to unwrap optionals in these same contexts.Resolves rdar://58302667