Description
rust-analyzer version:
- 0.3.1885-standalone (b6d1887 2024-03-17)
- 0.4.1889-standalone (5e276ae 2024-03-20)
- 0.0.0 (8d74705 2024-03-21)
rustc version: rustc 1.79.0-nightly (a7e4de13c 2024-03-19)
relevant settings: N/A
repository link (if public, optional): N/A
code snippet to reproduce:
pub enum AA {
BB,
}
pub fn hang() -> AA {
const CONST: AA = AA::BB;
CONST
}
Hovering over either CONST
starts the hang and rust-analyzer becomes unresponsive, consuming about ~200MiB RAM per second in this case, though in other cases it can be much faster.
The server cannot be killed through hovering on the rust-analyzer
button on the lower bar or with rust-analyzer: Stop server
, and must be killed through the command line. It is either non-responsive or doesn't kill the process.
I can reproduce this consistently with recent rust-analyzer client and server, but only after updating rustc
from nightly-2024-03-19
(rustc 1.79.0-nightly (3c85e5624 2024-03-18)
) to nightly-2024-03-20
(rustc 1.79.0-nightly (a7e4de13c 2024-03-19)
) or later with rustup (override works too).