Niwaka
Niwaka
I guess this issue should be blocked on #196.
>I don't think it needs to be blocked. We can support swift_repr = "struct" for now, and save swift_repr = "class" for later. Ok. By the way, I said that...
Right now, I personally need this feature, so I have decided to implement it.
I found that returning `Result` works correctly without needing any PRs. But, I think that we need to add any tests for returning `Result`. I guess that the following test...
Could you share the minimal example?
@tmolitor-stud-tu Sorry for the delayed response and thank you for sharing the example. > If you point me in the right direction, I can create a pull request fixing this...
@tmolitor-stud-tu ```rust public func test() { __swift_bridge__$test() } @_cdecl("__swift_bridge__$swift_handler") func __swift_bridge__swift_handler (_ text: UnsafeMutableRawPointer) { swift_handler(text: RustString(ptr: text)) } ``` In your example, it seems like `__swift_bridge__swift_handler` isn't called in...
As far as I remember, this method is used on the Rust side. So, other swift modules shouldn't call this.
@tmolitor-stud-tu What linker do you use? > a full (non-minimal) example can be found over here: https://github.com/monal-im/Monal/tree/develop/rust Please note the sed invocation at the end of the build script fixing...
> This means the linker sees two binaries, one containing the rust stuff that wants a symbol named __swift_bridge__$swift_handler and the other (the swift one) not exporting that symbol even...