lunatic_sqlite_api breaks rust-analyzer (vscode) in a cargo workspace

[you-win]

OS: Windows 10
rustc: 1.69.0
rust-analyzer: v0.3.1506
vscode: 1.77.3

I am developing a project using Lunatic,

I have a cargo workspace containing:

• a submillisecond + lunatic-rs server
• a client that connects to the server and does not compile to wasm
• a project that contains shared code (only relevant since all projects in the workspace use this project)

When I have the entire workspace open, rust-analyzer emits the following errors and rust-analyzer stops highlighting errors:

This is due to this line in lunatic-rs and the lib.rs in lunatic not matching up.

This can be solved by adding a .vscode/settings.json file like so:

{
    "rust-analyzer.cargo.target": "wasm32-wasi"
}

but then that breaks my client project, since that project is currently only configured to run on desktop targets.

Attempting to add compilation gates like this to lunatic-rs/src/sqlite/query.rs:

#[cfg(not(target_arch = "wasm32"))]
use lunatic_sqlite_api as bindings;

and exposing the relevant functions in lunatic/crates/lunatic-sqlite-api/src/sqlite_bindings.rs does not work, as the function arities are different.

[bkolobara]

Thanks @you-win for investigating this!

At one point I updated lunatic to be able to compile (but not link, I believe) on non-wasm32 targets. This significantly improved the situation with the tooling like rust-analyzer. With the introduction of the lunatic-sqlite-api crate we are sharing code between the native and wasm implementations again. This means that we have conditions based on targets and with some setups this can be an issue. Especially if you are sharing code between native and wasm implementations.

I think it should be possible to move the shared code into a separate crate imported by both and eliminate the conditional compilation issues.