Andrej Mihajlov

Results 371 comments of Andrej Mihajlov

Yeah that's right. All types end up in the same framework. Ok so I guess what I want is the following: I want Swift bindings for Rust types in a...

Not sure I understand what that prunning is about. However essentially all structs and types marked with uniffi derive macros, like Record, or Enum are being generated into Swift types....

This is not what I observe: ```rs let connectivity_sender = Arc::new(ConnectivitySender::new(connectivity_tx)); network_monitor.add_connectivity_observer(connectivity_sender.clone()); network_monitor.add_connectivity_observer(connectivity_sender); ``` The method on Kotlin side: ```kt internal fun addConnectivityObserver(observer: ConnectivityObserver) { if (observers.contains(observer)) { Timber.d("Contains such...

I have dropped `with_foreign` from `ConnectivityObserver` export and implemented `PartialEq + Eq + std::hash::Hash` for a concrete impl of `ConnectivityObserver` however still no luck. I will probably stick to checking...

I am not sure how that can be implemented in Kotlin. However would it be possible to use `Arc::as_ptr()` to obtain the underlying pointer and use it for comparison? I...

> I think the issue here is that there's no way for traits to define `Eq` etc? I think this seems like a language constraint. I don’t think we can...

I think if all types implementing a certain trait, also implement `PartialEq`, then we could potentially make it work via `Any`, i.e as described in https://stackoverflow.com/a/33687996/351305

Recently we renamed some of our crates but relied on package_name override to maintain the original name. This created a situation when switching git branches, old and new, generate two...

Not sure if that's the way out but if Kotlin does not support `u128`, then we could default to `String` conversion. This is what I am doing at the moment...

Maybe pull https://github.com/nymtech/nym-vpn-client/commit/289acb83f61a48d3777da37ab8026fda3b846fa6 and try `cargo build -p nym-vpn-proto`. See what `tonic::include_proto!` expands to. To me it looked like all `bool` were prefixed with `super::`