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
Same issue that has been reported a few times popped up again: #10022. I'm using 1.89.0-nightly (255aa22 2025-06-19). This happen inside vscode on Ubuntu 24.04 if that makes a difference.
Reacted by Nicholas Obert, Oleks Pickle, Cooper Hanessian, GoodSoup03, Martin Pool and TeamDman
Switched to yesterday's nightly and it works fine.
I got the same error and have been unsuccessfully trying to understand the problem for legit 5 hours, just to see your issue. Life is tough
Is it a rustc issue though ? What should I roll-back ? Rust-analyzer ? Because I also tried multiple previous versions of it (actually, previous versions of the extension) and none worked, even when cargo cleaning and reloading the window/extensions
It's not a rustc issue, it's a rust-analyzer issue, but it only occurs when you're on a new nightly toolchain. So you can rollback to a nightly before rust-lang/rust#140748. Alternatively, set "rust-analyzer.cargo.extraEnv": { "RUSTUP_TOOLCHAIN": "stable" }, which will cause r-a to analyze stable std instead.
I got the same error and have been unsuccessfully trying to understand the problem for legit 5 hours, just to see your issue. Life is tough
Is it a rustc issue though ? What should I roll-back ? Rust-analyzer ? Because I also tried multiple previous versions of it (actually, previous versions of the extension) and none worked, even when cargo cleaning and reloading the window/extensions
This is caused by internal changes within rustc that not yet implemented in rust-analyzer, so basically rust-analyzer issue.
So, switching rust-analyzer versions won't work for now.
Switched to yesterday's nightly and it works fine.
I think what perry-blueberry meant with this comment is that they switched to yesterday(Of course, from the moment that they wrote the comment)'s nightly rustc without problematic change and it worked fine with it.
As #20056 has been merged, I think this would be fixed in next rust-analyzer releases, both nightly and stable.
Though we still have some remaining homeworks in #20058, I'll finish it soon
Reacted by Oleks Pickle, Martin Pool, Jesper Persson and Nico Wagner
Activity
Veykril commentedon Jun 20, 2025
Likely rust-lang/rust#140748 / #19929
perry-blueberry commentedon Jun 20, 2025
Switched to yesterday's nightly and it works fine.
brvtalcake commentedon Jun 22, 2025
I got the same error and have been unsuccessfully trying to understand the problem for legit 5 hours, just to see your issue. Life is tough
Is it a rustc issue though ? What should I roll-back ? Rust-analyzer ? Because I also tried multiple previous versions of it (actually, previous versions of the extension) and none worked, even when
cargo cleaning and reloading the window/extensionsChayimFriedman2 commentedon Jun 22, 2025
It's not a rustc issue, it's a rust-analyzer issue, but it only occurs when you're on a new nightly toolchain. So you can rollback to a nightly before rust-lang/rust#140748. Alternatively, set
"rust-analyzer.cargo.extraEnv": { "RUSTUP_TOOLCHAIN": "stable" }, which will cause r-a to analyze stable std instead.ShoyuVanilla commentedon Jun 22, 2025
This is caused by internal changes within rustc that not yet implemented in rust-analyzer, so basically rust-analyzer issue.
So, switching rust-analyzer versions won't work for now.
I think what perry-blueberry meant with this comment is that they switched to yesterday(Of course, from the moment that they wrote the comment)'s nightly rustc without problematic change and it worked fine with it.
ShoyuVanilla commentedon Jun 22, 2025
As #20056 has been merged, I think this would be fixed in next rust-analyzer releases, both nightly and stable.
Though we still have some remaining homeworks in #20058, I'll finish it soon
pretty_assertions::assert_eq!#20059 as a duplicate of this issueruniq commentedon Jul 5, 2025
I believe I'm hitting this on beta too.
ChayimFriedman2 commentedon Jul 5, 2025
@Veykril could it be that #20056 is not on beta?
Veykril commentedon Jul 6, 2025
Oh indeed, we need to backport that