Skip to content

[Strict memory safety] Show issues with unsafe constructs in the for..in loop #81884

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
May 31, 2025

Conversation

DougGregor
Copy link
Member

We weren't showing the unsafe uses when we determine that a for..in loop is unsafe. Do so, which generally means complaining about next() being unsafe. Fixes rdar://151237127

….in loop

We weren't showing the unsafe uses when we determine that a for..in
loop is unsafe. Do so, which generally means complaining about `next()`
being unsafe. Fixes rdar://151237127
@DougGregor
Copy link
Member Author

@swift-ci please smoke test

@DougGregor DougGregor enabled auto-merge May 31, 2025 01:44
@DougGregor DougGregor merged commit 5c3faaa into swiftlang:main May 31, 2025
3 checks passed
@DougGregor DougGregor deleted the unsafe-for-loop-uses branch May 31, 2025 20:40
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.

1 participant