show {unknown} type

[chenxiang0010]

The latest version of rustc (1.82.0) with rust-analyzer (2024-11-25) will appear {unknown} type prompt, the solution is to downgrade rustc to 1.81.0 or rust-analyzer to 2024-08-12. The computer configuration is win10 professional version, 22H2, 19045.4894, this is a company computer and cannot share data.

rust-analyzer version: 2024-11-25

rustc version: 1.82.0

editor or extension: VSCode 1.95.3

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

repository link (if public, optional): (eg. rust-analyzer)

code snippet to reproduce:

let content = fs::read_to_string(path)?;

[lnicola]

What does rustup component list show? And do you have any errors in the logs?

Also, please try this: #17759 (comment).

[RuelYasa]

Also, please try this: #17759 (comment).

Thanks —— this works for me.

The problem is seemingly related with crates-io mirrors in China, which is possibly not up-to-date. Therefore, it helps to disable mirrors.

[lnicola]

More likely, to your proxy settings which we don't propagate. See also #18511, which probably wouldn't have helped for the same reason.

[chenxiang0010]

Also, please try this: #17759 (comment).

Thanks —— this works for me.

The problem is seemingly related with crates-io mirrors in China, which is possibly not up-to-date. Therefore, it helps to disable mirrors.

According to this review, cargo metada indicates that the standard library depends on a higher version of the library than the current PC configuration's mirror source, For example, the rand configuration version is 0.9.0, but the mirror source is only 0.8.5. After modifying the version owned by the image source according to the prompt of "cargo metada", the type " unknown " error is gone