std::fs::write inside of proc-macro breaks intellisense

[xxshady]

rust-analyzer version: 0.3.1958-standalone (5bf2f85 2024-05-09)

rustc version: 1.77.2

editor or extension: VSCode

code snippet to reproduce (UPDATED, again):

#[proc_macro_attribute]
pub fn repro(_: TokenStream, input: TokenStream) -> TokenStream {
    let crate_name = env!("CARGO_PKG_NAME");
    std::fs::write(format!("{crate_name}/repro"), "").unwrap();
    input
}

demo

bugged:

not bugged:

[Veykril]

This works fine for me with and without the fs access

[flodiebold]

It's a bad idea in general, though.

[xxshady]

This works fine for me with and without the fs access

@Veykril updated repro, for some reason it only happens when file is created inside of some directory

[Veykril]

will check later, but is the macro perhaps panicking on your system for some reason? (that is is it hitting the unwrap) Cause then this is expected

[xxshady]

no, its not panicking

[Veykril]

Are you sure it doesn't? Because it does for me

[xxshady]

are you on linux? because i'm on windows, i updated repro again xd, old one stopped reproducing for me

5-18-2024.19-42-28.mp4

[Veykril]

I am on windows as well, can you enable the setting "rust-analyzer.diagnostics.experimental.enable": true,? Just realized that macro errrors are still gated so you wont see proc-macros panic by default (we should change that)

[xxshady]

oh, i see, yes, it was panic in proc-macro

but why i can still see (some?) panics without enabling this experimental setting?

[Veykril]

The latter one comes from rustc that we just display inline as part of running cargo check on save

[xxshady]

ah, so proc-macro runs two times in workspace workdir, and in crate workdir, thats why file was creating