Niwaka
Niwaka
### Handling the same type declaration across multiple bridge modules >Even if it has method declarations across multiple bridge modules? I agree with "Potential Solution 2 - Don't allow mutable...
By the way, I guess that a Sendable `OpaqueRustType` couldn't have mutable arguments and owned arguments, like so: ```rust #[swift_bridge] mod ffi { extern "Rust" { type SomeType2; } extern...
>I don't think that this would be a problem. Let's say that we have two `Task`s and have two `OpaqueRustType`s on the Swift side, like so: ```rust #[swift_bridge] mod ffi...
>Can you move a Task to a different thread if it captures non Sendable values? Yes. But, Swift6 should generate any compile errors when a `Task` captures non `Sendable` values....
@chinedufn This issue should be separated into multiple tasks: - [ ] Supports `Sendable` for `OpaqueRustType` - [ ] Supports `Sendable` for `OpaqueRustType` across multiple bridge modules I'd like to...
If a opaque type implements `Error`, the opaque type can't have owned methods for now.
You should write "export PYTHONIOENCODING=utf-8" to environment file.(e.g. ~/.basrc)
@nafehshoaib > Any updates on this? Not yet. > Would love to use failable initializers instead of a static methods that return optionals I guess that I can implement this...
@chinedufn Can I implement this feature?
Next, I'll implement throwing initializers. I'd like to use this feature.