Cannot infer type with version `0.3.3`

[LucaCappelletti94]

Hi, while running cargo check with the following rust version:

rustup 1.28.1 (f9edccde0 2025-03-05)
info: This is the version for the rustup toolchain manager, not the rustc compiler.
info: The currently active `rustc` version is `rustc 1.88.0-nightly (2fa8b11f0 2025-04-06)`

I got the following error:

error[E0282]: type annotations needed
   --> /home/luca/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/sqlite-wasm-rs-0.3.3/src/vfs/utils.rs:104:38
    |
104 |         src.len() == dst.length() as _,
    |                                      ^ cannot infer type

I will try to make a PR shortly to try and address this.

[Spxg]

I tried it successfully. Can you tell me the environment and commands you executed?

[LucaCappelletti94]

I have import the sqlite-wasm-rs crate as follows:

sqlite-wasm-rs = { version = "0.3", default-features = false, features = [
  "precompiled",
] }

Just to provide the same thing, when I either run cargo check (which loads the target from the .cargo directory) or cargo check --target wasm32-unknown-unknown, I get the following:

Fortunately, the PR necessary #59 is very small. We can always safely cast a u32 to a usize when compiling for a wasm32 target.

[Spxg]

Fortunately, the PR necessary #59 is very small. We can always safely cast a u32 to a usize when compiling for a wasm32 target.

First of all, thank you for reporting and fixing this problem. The PR looks good to me and will be merged later, but I still want to know why it went wrong. It may be a compiler bug. CI has tested the compilation of different systems and has never had this problem. Can you test the compilation of the stable version of rustc?

[LucaCappelletti94]

With rustc 1.86.0 (05f9846f8 2025-03-31), as determined by running rustc --version, the cargo check gives me the same error. I am working in a workspace environment, but other than that nothing particularly odd comes to mind.

Nevertheless, the odd error persists:

error[E0282]: type annotations needed
   --> /home/luca/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/sqlite-wasm-rs-0.3.3/src/vfs/utils.rs:104:38
    |
104 |         src.len() == dst.length() as _,
    |                                      ^ cannot infer type

For more information about this error, try `rustc --explain E0282`.
error: could not compile `sqlite-wasm-rs` (lib) due to 1 previous error
warning: build failed, waiting for other jobs to finish...

[Spxg]

https://github.com/earth-metabolome-initiative/emi-monorepo/blob/f15938b8ea39fbd5156ac6c02945c3fc800ffac3/web/frontend/Cargo.toml#L34

It is this dependency that causes the compiler error, but the reason is unknown. I will continue to look at it. Actually it is caused by gloo-net = "0.1.0"

[LucaCappelletti94]

I had not yet published the edits that include the sqlite-wasm-rs. Did you manage to reproduce this issue without the sqlite-wasm-rs dependency?

The error reported would appear to be in sqlite-wasm-rs, not some other crate, but I cannot exclude this may be happening due to some odd dependency shenanigans.

I have now pushed the edits including the sqlite-wasm-rs crate, note that right now it is imported in the frontend Cargo.toml - do note that right now I am importing it from my fork and you would need to change this:

sqlite-wasm-rs = { git = "https://github.com/LucaCappelletti94/sqlite-wasm-rs.git", default-features = false, features = [
  "precompiled",
] }

to this:

sqlite-wasm-rs = { version = "0.3", default-features = false, features = [
  "precompiled",
] }

I am certain all of the above is already well known to you but since the error seems to be rather peculiar I thought it best to be as clear as possible.

Just navigate to /emi-monorepo/web/frontend and run cargo check there to hopefully reproduce the issue.

[Spxg]

I had not yet published the edits that include the sqlite-wasm-rs. Did you manage to reproduce this issue without the sqlite-wasm-rs dependency?

I have just tried adding the sqlite-wasm-rs dependency and confirmed that the problem is caused by reqwasm, to be precise, gloo-net 0.1.0~0.2.4. You can remove the reqwasm dependency and use gloo-net = 0.6.0, which should solve the problem.

[Spxg]

to be precise, gloo-net 0.1.0~0.2.4

It seems that there will be problems when the serde-serialize feature of wasm-bindgen is turned on.

[LucaCappelletti94]

Always with the same error or due to something else?

While I agree that in this specific case I may just remove that dependency, wouldn't it be better to fix the relatively simple issue it causes?

[LucaCappelletti94]

Before proceeding to close to issue, could you share what problem you have encountered with the serde-serialize feature of wasm-bindgen ?

[Spxg]

Before proceeding to close to issue, could you share what problem you have encountered with the serde-serialize feature of wasm-bindgen ?

Honestly, this is a bit weird. rust-lang/rust#140262