Mark Hammond
Mark Hammond
hi, thanks for looking at uniffi! We'd be happy to look at zero (ish?) cost improvements to our diagnostics here.
Let's call this fixed by #2564, but we'd welcome more improvements or concrete problem cases in new PRs/issues.
b/w compat will be the issue here, but we could probably have a flag in uniffi.toml to change this.
It can't really work in general, because the signature exposed by the bindings needs to be one of the "primitive" types for that language - ie, something needs to know...
That's a very elaborate proposal, but it's difficult to comment without more specifics. Ultimately though, it sounds like calling back into Kotlin from Rust created threads are causing you problems,...
Ah, I think I was referring to https://github.com/mozilla/application-services/blob/main/docs/android-faqs.md#what-challenges-exist-when-calling-back-into-kotlin-from-rust - which does describe the problem but doesn't really offer any solutions.
The checksums are to try and ensure the correct library is loaded at runtime, which the build process can't really ensure. #1789 also notes that the checksums aren't particularly adequate...
sorry I missed this before: > I do also have a question regarding the use of these macros: > When are they required or recommended around a COM call? They...
I don't see why not - it seems like we should be consistent!
I'm fairly sure I saw firefox-ios using this (or maybe I'm mistaken and it's difficult to test :( #2319 allows you to turn it off, maybe we could default it...