You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hovering over Provenance, RA shows this trait. It seems to think that this is actually using dyn Provenance as a type here. However that is wrong, the name Provenance in this scope refers to this type. Looks like somewhere the precedence of blog imports is going wrong.
"rust-analyzer.lens.enable": false,
"rust-analyzer.cargo.buildScripts.useRustcWrapper": false,
"rust-analyzer.cargo.buildScripts.enable": true,
"rust-analyzer.procMacro.enable": true,
"rust-analyzer.diagnostics.disabled": [
"unlinked-file", // I guess for "normal" projects unlinked files are strange, for me they are common
"unresolved-module", // https://github.com/rust-lang/rust-analyzer/issues/9173
"type-mismatch", // https://github.com/rust-lang/rust-analyzer/issues/1109
],
To reproduce, check out Miri and follow the setup described here. Then open, for example, this code:
Hovering over
Provenance
, RA shows this trait. It seems to think that this is actually usingdyn Provenance
as a type here. However that is wrong, the nameProvenance
in this scope refers to this type. Looks like somewhere the precedence of blog imports is going wrong.rust-analyzer version: rust-analyzer version: 0.3.1221-standalone
rustc version: rustc 1.66.0-nightly (85d089b41 2022-10-25)
relevant settings:
The text was updated successfully, but these errors were encountered: