You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
No description provided.
The text was updated successfully, but these errors were encountered: