mismatched-arg-count: expected 0 arguments, found 1;

[ethever]

rust-analyzer version: (eg. output of "rust-analyzer: Show RA Version" command, accessible in VSCode via Ctrl/⌘+Shift+P)

v0.3.1533

rustc version: (eg. output of rustc -V)

$ rustc -V
rustc 1.69.0 (84c898d65 2023-04-16)

relevant settings: (eg. client settings, or environment variables like CARGO, RUSTC, RUSTUP_HOME or CARGO_HOME)
no

Problem:

In https://github.com/rkusa/sqlite-vfs/blob/f60cad5ae21aed9ff5d6e4030036750f39440a71/src/lib.rs#LL907C26-L907C26 this repo (sqlite-vfs crate), the rust-analysis find a parameter related error in the code line 907 (you can find it in the previous link), but cargo build works.

$ cargo build --target wasm32-unknown-unknown --release
Compiling log v0.4.18
Compiling time-core v0.1.1
Compiling time v0.3.21
Compiling sqlite-vfs v0.2.0 (/root/projects/sqlite-vfs)
Finished release [optimized] target(s) in 1.49s

[ethever]

any infomation needed i am happy to provided.

[lowr]

This is rust-lang/chalk#727. I think this is pretty much the same problem this comment explains and I'm not sure what it'd take to fix this.

We ask chalk to check if V: WalIndex holds (because WalIndex also has delete() method). Chalk takes implied bounds into account, thinks it can prove it if <?0 as DatabaseHandle>::WalIndex == V holds. Obviously it doesn't hold, but chalk cannot see that currently. Chalk responds back to us that the goal may or may not hold (i.e. Solution::Ambig), which we take as affirmation, leading to wrong method resolution.