rust-block VS swift-bridge

let block = ConcreteBlock::new(move |key: *const c_char, value: xpc_object_t| { unsafe { xpc_retain(value) }; let str_key = unsafe { CStr::from_ptr(key).to_string_lossy().to_string() }; let xpc_object: XPCObject = value.into(); map_refcell .borrow_mut() .insert(str_key, xpc_object.into()); true }); // https://github.com/SSheldon/rust-block#creating-blocks let block = block.copy(); let ok = unsafe { xpc_dictionary_apply(object.as_ptr(), &*block as *const _ as *mut _) };

A bit late, but `swift-bridge` (https://github.com/chinedufn/swift-bridge) does this intelligently, and is probably what you're looking for.

4) Another route that I tried is to develop a simple terminal app using SwiftUI with a Xcode project to build that app + link against a Rust library compiled for iOS with the actual logic. I used swift-bridge for this and it works really well, to the point where I have a custom logger that you can simply use the print stuff to SwiftUI from Rust using the log crate. Once I have a bit more time, I will probably try figuring out how to clean this up a bit more.

Since Swift is your first target, I might recommend swift-bridge which can generate bindings for Rust async fns that Swift can call directly.

I'm working on getting my GUI crate (https://github.com/audulus/rui) working on iOS (https://github.com/audulus/rui-ios). Multitouch will be fun. Shout out to the excellent work in swift-bridge: https://github.com/chinedufn/swift-bridge.

So that class SwiftString was actually unused. I've removed it here https://github.com/chinedufn/swift-bridge/pull/33 .

Here's an example of a Rust library that exposes an async function that uses reqwest to make an API call, and a main.swift that calls that async function.

Have you tried Swift Bridge? https://github.com/chinedufn/swift-bridge