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
Execute cargo clean to solve the compilation pass. Why directly execute cargo b to report this error
~ cargo b
...
...
Checking webpki-roots v0.22.5
Checking cpufeatures v0.2.5
Checking polling v2.4.0
Checking async-channel v1.7.1
Checking tokio-rustls v0.23.4
Checking thiserror v1.0.37
Checking rust_decimal v1.26.1
Checking sha1 v0.10.5
Checking async-lock v2.6.0
error[E0554]: `#![feature]` may not be used on the stable release channel
--> /Users/baoyachi/.cargo/registry/src/crates.io/thiserror-1.0.37/src/lib.rs:238:34
|
238 |#![cfg_attr(provide_any, feature(provide_any))]| ^^^^^^^^^^^
For more information about this error, try `rustc --explain E0554`.
error: could not compile `thiserror` due to previous error
warning: build failed, waiting for other jobs to finish...
I read the thread (and other referenced threads). Seems that almost all people eventually found that it was a bug from rust-analyzer1, and it already got fixed. I am not sure if there is anything Cargo can do. If rust-analzyer needs to coordinate with Cargo we're happy to.
Going to close this out soon. If you think it's wrong, please attach a reproducible example to help the investigation.
(I cannot reproduce this either)
Problem
Execute
cargo clean
to solve the compilation pass. Why directly execute cargo b to report this errorThe Detail error: dtolnay/thiserror#192
Steps
No response
Possible Solution(s)
dtolnay/thiserror#192
Notes
No response
Version
The text was updated successfully, but these errors were encountered: