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

Will this lib consider sendable? #1266

Open
Horse888 opened this issue Apr 25, 2024 · 1 comment
Open

Will this lib consider sendable? #1266

Horse888 opened this issue Apr 25, 2024 · 1 comment

Comments

@Horse888
Copy link

No description provided.

@zaphoyd
Copy link

zaphoyd commented Dec 27, 2024

I'm also interested in this answer. With the move to more strict Swift 6 concurrency there are a few objects that are advertised as and appear to be thread safe, but are not marked as such at the language level and as a result cannot be used with strict concurrency checking.

The primary one that would help us right now is the Connection object. Its only property right now is _handle which technically is a variable optional, however, it is always initialized in the constructor and never changed. Is there any reason this couldn't be a constant, non-optional and the Connection be marked Sendable?

Edit: the OpaquePointer might complicate fully checked Sendable marking as there is no way for the swift compiler to check it. @unchecked Sendable on connection might be appropriate?

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

No branches or pull requests

2 participants