Chinedu Francis Nwafili

Sounds good!

A Swift `Error` must implement `Sendable`, so I'm not sure that we would want `#[swift_bridge(Error)]` support without nailing down our send/sync story. It looks like the `localizedDescription` is available on...

Hey, thanks for opening this issue. --- https://github.com/chinedufn/swift-bridge/pull/202 should fix the dangling pointer warning. --- As for the the signatures that you mention, thus far `swift-bridge` has been biased towards...

Submitted a PR for `Option` in Swift functions https://github.com/chinedufn/swift-bridge/pull/203 . Mind reviewing it?

The first comment was written before we had the `BridgeableType` trait. I'm not sure what the best abstraction is here. It's hard to say within feeling it out a bit....

Good idea. > It should probably return nil if the RustVec isn't owned. It isn't possible to borrow a `RustVec` today. In the future when we supported borrowing we would...

Whether or not we should support `RustString + RustString` comes down to whether or not we expect people to understand that this will cause an allocation. I think that it's...

I hadn't heard of this feature. Yeah this sounds like something that we want to support. https://docs.swift.org/swift-book/documentation/the-swift-programming-language/initialization/#Failable-Initializers I'm thinking we should also add a `#[swift_bridge(init)]` section to the `Function Attributes`...

Yeah that would be great. I think "Failable Initializers" are ones that return an `Option`. We can refer to inits that can throw as "Throwing Initializers". Feel free to implement...

Released in `0.1.57` https://crates.io/crates/swift-bridge/0.1.57