Open pacu opened 5 months ago
It's not exactly related to the other issue. In my understanding, you are changing the function signature when you do not enable the feature (you remove the 4th parameter), so you have to add the same #[cfg()]
annotation in the caller's 4th argument to remove it too.
uniffi = "0.27.0"
Problem:
cfg(feature = )
anduniffi::export
macros don't get alongcontext:
I'm working on this FROST signatures wrapper with uniffi. https://github.com/pacu/frost-mobile-sdk
I can build the FROST dependency with or without the
redpallas
feature flag. That would change some arguments on the FFI exposed to the client.This works fine if I build the project with the
redpallas
feature enabled. But it fails when I don't enable it.Is this expected as a limitation of uniffi? or is it real problem?
possibly related:
https://github.com/mozilla/uniffi-rs/issues/2000