call to unsafe function is unsafe and requires an unsafe function or block

[aurexav]

I don't think there is any unsafe code.

This is a serious regression in nightly and it's important to fix it before the next release.

[aurexav]

A fresh installation resolves this issue, but I'm not certain why.

However, it reappears after a while.

[ChayimFriedman2]

This is probably caused by an outdated version of rust-analyzer you use. See #18842.

[aurexav]

This is probably caused by an outdated version of rust-analyzer you use. See #18842.

It's not installed locally. It was installed by the VSC plugin. However, I'm not sure if VSC update the package correctly. I've tried reinstalling the plugin, but the problem persists.

[ChayimFriedman2]

I can't reproduce the problem (with a rust-analyzer prerelease version) on nightly or stable toolchain, so this is probably not a problem in r-a.

[aurexav]

A fresh install of vscode-insiders also gets this error. Interesting.

[ChayimFriedman2]

Do you also get the same error on a clean project with a call to vec![]?

[aurexav]

Do you also get the same error on a clean project with a call to vec![]?

But empty vec! works.

[aurexav]

rustup component add rust-analyzer resolves this issue, preventing the use of the one shipped with VSC extension.

[ChayimFriedman2]

Weird, now I get the same error on rust-analyzer invocations of vec![].

[aurexav]

Weird, now I get the same error on rust-analyzer invocations of vec![].

This is similar to the situation here. It seems quite unstable, appearing and disappearing randomly. All the solutions that I provided above are only temporary fixes.

[ChayimFriedman2]

Found that sneaky bug!

[RReverser]

Thanks! I was very confused when Rust-Analyzer started marking functions like atan2 or asin as unsafe.

[Veykril]

That bug probably marked half the standard library as unsafe. There is a new nightly release out with the fix now.