Skip to content

add coverage for <<error-type>> + Sendable diagnostic issue #41635

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
Mar 4, 2022

Conversation

kavon
Copy link
Member

@kavon kavon commented Mar 2, 2022

when a variable with type <<error-type>> was captured in a
sendable function's environment, we use to emit a diagnostic
about it not being sendable, but it's for a bogus type.

at some point this issue disappeared as the sendable implementation
evolved, but this commit adds regression coverage.

resolves rdar://82452688

@kavon
Copy link
Member Author

kavon commented Mar 2, 2022

@swift-ci please smoke test and merge

when a variable with type `<<error-type>>` was captured in a
sendable function's environment, we use to emit a diagnostic
about it not being sendable, but it's for a bogus type.

at some point this issue disappeared as the sendable implementation
evolved, but this commit adds regression coverage.

resolves rdar://82452688
@kavon kavon force-pushed the testcoverage-82452688 branch from 41d8577 to e8e27a7 Compare March 4, 2022 02:09
@kavon
Copy link
Member Author

kavon commented Mar 4, 2022

@swift-ci please smoke test and merge

@swift-ci swift-ci merged commit a116397 into swiftlang:main Mar 4, 2022
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