Skip to content

[Diagnostics] Ignore result type failures if one side is a hole #38235

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 2 commits into from
Jul 6, 2021

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Jul 2, 2021

If one of the sides in a application result conversion is a hole
it could only mean that the fix has been recorded earlier (at the
point where hole was introduced) and failure at function result
position could be safely ignored.

Resolves: rdar://79757320

Instead of preserving unresolved dependent member types, let's resolve
them as holes if their base has been determined to be one.
@xedin xedin requested a review from hborla July 2, 2021 19:58
@xedin
Copy link
Contributor Author

xedin commented Jul 2, 2021

@swift-ci please smoke test

If one of the sides in a application result conversion is a hole
it could only mean that the fix has been recorded earlier (at the
point where hole was introduced) and failure at function result
position could be safely ignored.

Resolves: rdar://79757320
@xedin
Copy link
Contributor Author

xedin commented Jul 6, 2021

I managed to reduce the example and remove SwiftUI dependency from the test-case.

@xedin
Copy link
Contributor Author

xedin commented Jul 6, 2021

@swift-ci please smoke test

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