Chinedu Francis Nwafili

Sweet idea! I wonder if it's possible to make this a non-breaking change? i.e. exposing a function in `skeletal-animation-system` that converts landon format to this one .. or something .....

Hey. I don't see `Option` in your error message at all. That's peculiar. It makes me uncertain about whether or not your error message came from that example? --- At...

> This issue is likely related to or a duplicate of https://github.com/chinedufn/psd/issues/26 @bram-dingelstad not sure if you found a different solution, but if not I'd be happy to review a...

Do you mean opaque Rust types or transparent shared structs? Can you comment with a bridge module illustrating what you mean?

Ok, I think I have a potential solution in mind. Here are some thoughts: --- Imagine the following bridge module: ```rust #[swift_bridge::bridge] mod ffi { extern "Rust" { type MySendSyncType;...

Hmm, that's a good question. `isOwned` gets modified when - (case 1) the `deinit` method on a `class OpaqueRustType` instance is called. - (case 2) you pass on owned `class...

> This means that its resources get released from only deinit I think that we'll eventually want to be able to explicitly pass ownership of `Sendable` opaque Rust types from...

> How about this? Sounds about right to me! > If we adopt the idea immediately above, we don't need to care about this since we couldn't have owned methods...

Sorry I'm not very familiar with Swift `Task`s. If all of that code is running on the same thread then it looks thread safe to me. Why wouldn't this be...

Nice thanks for researching this. --- So, even if we tried to prevent methods that take owned arguments a user could always do: ```swift let opaqueRustType2 = OpaqueRustType2() //Task1 Task...