Manish Goregaokar

I'm also happy to help folks understand the tool better to use in integration; [the book](https://rust-diplomat.github.io/book/) does document a bunch of stuff but not everything

link fixed. We do support result types, they turn into a union in C, a std::variant-wrapper in C++, and an exception in JS we have a way to return strings...

> The documentation on Writeable only covers someone passing in a "String", not Rust code returning Strings. That's where there is some ugliness right now dealing with strings in C...

So for your API I would write something like this: ```rust #[diplomat::bridge] mod ffi { use diplomat_runtime::DiplomatWriteable; use std::fmt::Write; #[diplomat::opaque] struct Thingy; impl Thingy { pub fn set_mathml(input: &str, out:...

> Just to make sure I understand the C++ interface correctly: C, not C++. C++ is nicer; it takes a `std::string_view` and returns a result wrapper around a `std::string`. I...

> I need both the C and C++ interfaces, plus I'd really like to have a JS interface Yep, we have all three. The C and C++ ones have been...

It's easy enough to generate, but yeah perhaps worth waiting on advertising it

Pretty busy right now, can't promise anything. @sffc might be interested in trying?

Diplomat's API definitions are also a subset of Rust, so while I don't think much Rust experience is required, it may be annoying for them to have to pick it...

Reexport just means that `Client` gets the same method that proxies to the room