Graph Limitations on Rust targeting WASM?

[davidhmays]

I'm hoping to use CozoDB as a local first database in either a Dioxus or Tauri project.
This would involve using the Rust version of CozoDB. I believe the Rust in these projects gets compiled to Web Assembly?

If the Rust code is compiled to WASM, will CozoDB have the same limitations listed below for the "browser" version?
If so, it sounds like it would not have the graph module available and that's a main part of why I want to use it.

And how does the browser playground in the tutorial not face this limitation?

If you are using Cozo in browser, Constant is the only fixed rule you can use. In all other cases your Cozo would have the graph algorithms module enabled, and all graph algorithms are implemented as fixed rules.

[davidhmays]

What I've found so far:

While the WASM variant of CozoDB says it doesn't support all of the graph features, the Cozo DB Rust support says it works on any target that supports the std library.
If using Dioxus (which is built on Tauri) the Dioxus web has you add wasm-32-unknown-unknown which does appear to support the std library

I'll still have to just try it and see what runs.

[davidhmays]

Adding cozo ="0.7.5" to a Dioxus web project results in the following when running dx serve:

Serving project failed: error: the wasm*-unknown-unknown targets are not
supported by default, you may need to enable the "js" feature. For more information s
ee: https://docs.rs/getrandom/#webassembly-support

[davidhmays]

Trying to add getrandom = { version = "0.2", features = ["js"] } as suggested by the link above results in:

--- stderr error occurred: Failed to find tool. Is clang installed? (see https://github.com/
rust-lang/cc-rs#compile-time-requirements for help)

Though if the Dioxus is running the Rust in WASM mode, I'm not sure that a "js" flag is the correct setting, but I don't see any other options in the above link for other options.