Niwaka

Thank you for the invitation!!!! I'm honored and grateful for the opportunity to contribute more as a collaborator!!!!!! Thank you again!!!!

Please add https://docs.swift.org/swift-book/LanguageGuide/Concurrency.html to Resources.

First of all, how about supporting Swift's `Sendable` protocol when fields of Rust's `struct` consist of only `primitive` types such as `bool`?

>Do you mean opaque Rust types or transparent shared structs? I meant opaque Rust types. >Can you comment with a bridge module illustrating what you mean? ```Rust #[swift_bridge::bridge] mod ffi...

>Could Swift's Actors be of use here? I don't think so. Swift's `Actor`s is related to Swift's `Task`. Swift's `Actor` can be accessed by only one Swift's `Task` at a...

If Opaque Rust Types have some methods with `&mut self`, we need to use `Arc` or something like that, like so. ```rust impl SomeType { fn some_method(&mut self) { self.0.lock().unwrap();...

Thank you for your quick reply. >Thoughts? I'll read it this weekend!! ## By the way, right now we can use multithreading on both Swift and Rust. So, I have...

>Idea 3 - Do nothing >One option is to just allow this to be a problem that the user must manage and document it (unless there's some Swift feature that...

>I'm imagining that the compile time error on functions that pass ownership from Swift -> Rust such as: Sounds good to me!! >Long term I like Idea 2 - Use...

Hi @chinedufn. Based on the previous discussion, To make the `OpaqueRustType` that conforms to `Sendable`: 1. Needs to conform to `Sync`+`Send` on the Rust side. 2. To release its resources...