As of nightly 2021-08-25, most macros cause `missing-unsafe` errors

[AaronKutch]

Since some recent nightly (In the past week or two since I've updated), rust-analyzer is almost unusable for me on large codebases because of the number of errors produced.

A program as simple as this one:

fn main() {
    dbg!("hello?");
}

produces "this operation is unsafe and requires an unsafe function or block"

edit: actually, I don't know if my rust-analyzer is nightly, but I know it was updated just today

[matklad]

I believe that's fixed in #10032, will be in the next nightly!

Thanks for opening the issue and pinging me! I've kicked the nightly release, so that "next nightly" happens in ~20 minutes!

EDIT: the build https://github.com/rust-analyzer/rust-analyzer/actions/runs/1171225035

[OfekShochat]

thank you, happened to me too!

EDIT: it doesnt happen in the build you sent @lnicola

[lnicola]

Let's close this as a duplicate of #10022. We can reopen it if it still happens in nightly or in the next release.

[akhilman]

I have the same error in rust-analyzer 996300f 2021-09-05 dev

[bjorn3]

Your rust-analyzer version is from 15 days ago. Updating it to the latest version should fix the problem.

[akhilman]

996300f seems to be latest version provided by rustup nightly toolchain components

[lnicola]

Yeah, that's expected. There were some problems updating the rustup version. You can keep an eye on rust-lang/rust#88685.

[bjorn3]

The rustup version will be updated in rust-lang/rust#88685. If you are lucky it will be included in the next rustc nightly.

[bionicles]

somehow this surfaced for me in 2025!

[mlp1802]

My project is LITTERED with "unsafe" errors for "vec![]". How is this even possible? using today's toolchain but the problem was there for the older nightly toolchain as well.

[lnicola]

@mlp1802 #18842.