Skip to content

[concurrency - 6.0] declare POSIXErrorCode as Sendable #75001

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

Conversation

glessard
Copy link
Contributor

@glessard glessard commented Jul 5, 2024

This change makes POSIXErrorCode a Sendable type. POSIXErrorCode is an enum that simply maps an Int32 value.
It isn't frozen, though, so it is not inferred as Sendable.

Addresses: rdar://99047401
Original PR: #75000
Risk: Very low. This change has no ABI implication; it simply removes possible errors in language mode 6.
Reviewers: @Azoy, @parkera

@glessard glessard requested a review from a team as a code owner July 5, 2024 20:59
@glessard
Copy link
Contributor Author

glessard commented Jul 5, 2024

@swift-ci please test

@glessard glessard enabled auto-merge July 5, 2024 21:02
@glessard glessard added 🍒 release cherry pick Flag: Release branch cherry picks Concurrencу Area → standard library: The `Concurrency` module under the standard library umbrella Sendable Area → standard library: The Sendable protocol labels Jul 5, 2024
@glessard glessard changed the title [concurrency] declare POSIXErrorCode as Sendable [concurrency - 6.0] declare POSIXErrorCode as Sendable Jul 5, 2024
@glessard glessard merged commit f8774c3 into swiftlang:release/6.0 Jul 6, 2024
4 of 5 checks passed
@glessard glessard deleted the rdar99047401-err-nosendable-6.0 branch July 6, 2024 05:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Concurrencу Area → standard library: The `Concurrency` module under the standard library umbrella 🍒 release cherry pick Flag: Release branch cherry picks Sendable Area → standard library: The Sendable protocol
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants