-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Start stubbing out more parts of Type::join(). #14698
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@swift-ci Please smoke test |
@swift-could test source compatibility |
@swift-ci test source compatibility |
@swift-ci Please smoke test |
@swift-ci Please test source compatibility |
@swift-ci Please smoke test |
@swift-ci Please test source compatibility |
1 similar comment
@swift-ci Please test source compatibility |
@swift-ci Please smoke test |
@swift-ci Please test source compatibility |
@swift-ci Please smoke test |
1 similar comment
@swift-ci Please smoke test |
@swift-ci Please test source compatibility |
1 similar comment
@swift-ci Please test source compatibility |
Improve support for Optional among other things. Return Any when it is really the best answer given the types involved, or nullptr if we cannot yet produce an accurate result. This implementation returns Any? when joining Any with an Optional<T>. In our type system both Any and Any? are effectively subtypes of one another since each can hold all the values that the other can hold. So this choice is somewhat arbitrary, but does line up nicely with the notion that T is always a subtype of T?.
@swift-ci Please smoke test |
@swift-ci Please test source compatibility |
1 similar comment
@swift-ci Please test source compatibility |
Improve support for Optional among other things.
Return Any when it is really the best answer given the types involved,
or nullptr if we cannot yet produce an accurate result.