-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty RUSTFLAGS
are still set
#1496
Comments
Could you test #1498 |
could this be related in any way? #1419 |
@domenkozar this unfortunately does not work, as it appears that
|
@delehef we can't dynamically filter I've pushed a fix that sets it to |
Just FYI, I tested it on my side and it didn't fail; I suppose you would need to alter
This one seems to work fine :) |
Alright merged, thanks! |
Describe the bug
Even if the computed value is empty, the
RUSTFLAGS
env. var. is still set when activating rust withlanguages.rust.enable = true;
.However, an empty
RUSTFLAGS
env. var. inhibits any rust flags that may have been set in.cargo/config.toml
.To reproduce
Set some rust flags in the
[build]
section of.cargo/config.toml
, do not alterlanguages.rust.rustflags
, and enable the rust environment withlanguages.rust.enable = true;
.Version
devenv 1.1.0
The text was updated successfully, but these errors were encountered: