Skip to content
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

[6.1] Remove incorrect guard check for Android (#5171) #5175

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

finagolfin
Copy link
Member

Explanation: This guard check currently always fails on Android because spawnAttrs is set to nil on Android just two lines above. There was some talk of making changes to the Android NDK upstream or nullability annotations instead by @hyp a couple months ago, which is why we left this in temporarily, but nothing came of it and he hasn't responded in months, so let's just fix this for now.

Scope: Only affects Android

Issue: None

Original PR: #5171

Risk: None

Testing: I apply this patch on my Android CI for the last couple months, works well.

Reviewer: @hyp

@itingliu, mind reviewing?

@finagolfin
Copy link
Member Author

@swift-ci please test

@finagolfin finagolfin changed the title Remove incorrect guard check for Android (#5171) [6.1]Remove incorrect guard check for Android (#5171) Feb 22, 2025
@finagolfin finagolfin changed the title [6.1]Remove incorrect guard check for Android (#5171) [6.1] Remove incorrect guard check for Android (#5171) Feb 22, 2025
@parkera parkera requested a review from itingliu February 24, 2025 19:05
@parkera
Copy link
Contributor

parkera commented Feb 24, 2025

adding @itingliu for visibility, but this looks good to me too

@parkera parkera merged commit 12f2026 into swiftlang:release/6.1 Feb 24, 2025
2 checks passed
@finagolfin finagolfin deleted the droid branch February 25, 2025 14:19
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