[SE-0352] Amendment to open existential arguments for optional parameters #1797
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.
SE-0352 "Implicitly Opened Existentials" has a limitation that prevents the opening of an existential argument when the corresponding parameter is optional. This amendment proposes to change that behavior, so that such a call will succeed when a (non-optional) existential argument is passed to a parameter of optional type:
The rationale for not opening the existential
p
in the first call was to ensure consistent behavior with the second call, in an effort to avoid confusion. However, experience with implicitly-opened existentials has shown that opening an existential argument in the first case is important, because many functions accept optional parameters. Additionally, the workaround requires a lot of boilerplate, writing a separate generic function.There is an implementation of this amendment at swiftlang/swift#61321