Skip to content

[TypeJoin] Return Unimplemented (aka Type()) for things we cannot yet… #20073

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

Merged
merged 1 commit into from
Oct 26, 2018
Merged

[TypeJoin] Return Unimplemented (aka Type()) for things we cannot yet… #20073

merged 1 commit into from
Oct 26, 2018

Conversation

rudkx
Copy link
Contributor

@rudkx rudkx commented Oct 26, 2018

… compute.

It's important not to return Any for joins that we cannot compute to
distinguish them from ones that we currently can compute but result in
Any.

I don't have a test case for this that is independent of other changes
that I have that are not yet ready to merge. With the testing
infrastructure we have for join we don't currently have a way to test
out cases that fail in this fashion.

… compute.

It's important not to return `Any` for joins that we cannot compute to
distinguish them from ones that we currently can compute but result in
`Any`.

I don't have a test case for this that is independent of other changes
that I have that are not yet ready to merge. With the testing
infrastructure we have for join we don't currently have a way to test
out cases that fail in this fashion.
@rudkx
Copy link
Contributor Author

rudkx commented Oct 26, 2018

@swift-ci Please smoke test

@rudkx rudkx merged commit 13cc0d0 into swiftlang:master Oct 26, 2018
@rudkx rudkx deleted the join-to-nowhere branch October 26, 2018 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants