VSCode doesn't restart the server when cargo.* settings change

[michaelgruenewald]

rust-analyzer version: 0.3.2593-standalone

rustc version: rustc 1.91.0-nightly

editor or extension: VSCode, extension version 0.3.2593

VSCode doesn't restart the server when any of the rust-analyzer.cargo settings change, e.g., rust-analyzer.cargo.cfgs or rust-analyzer.cargo.extraEnv. Especially these two setting can have significant changes though and should result in restarts.

Culprit appears to be this, that's missing "cargo" in the list.

[michaelgruenewald]

This appears to be broken since #20020 but that doesn't have any context.

[ChayimFriedman2]

They shouldn't require restart, I believe, they should work fine without it.

[michaelgruenewald]

This may only be a problem with proc macros, not sure. I can reproduce this by using env! in a proc macro, then changing the env variable contents. The type of the x variable in my example only changes after manually restarting the server. (This is two crates on one workspace.)

screencast-2025-10-15_13.12.17.mp4

[ChayimFriedman2]

Proc macros should not use env!() AFAIK, they should tell Cargo to watch the environment variable and read it at runtime.

[michaelgruenewald]

Looks like the underlying issue here is similar to the one described in #17593 and did actually get resolved with #20554.