Weihang Lo

Probably kinda a duplicate of . This has got more discussions so close that in favor of this. I'd say the relationship between libtest and cargo-test is a bit unclear...

Web requests might lead to wrong information. People can have a script called `cargo-expand` under `$PATH`, but has nothing to do with [`cargo-expand`](https://crates.io/crates/cargo-expand) on crates.io. To me, embedded description is...

I guess cargo maintainers here possibly have little knowledge about V8 and Deno stuff. It would be great if you can provide more contexts, such like - What exactly you're...

> if we could just setup all these configs… For configuring environment variables, it's available today in build script with [`cargo:rustc-env=VAR=VALUE`](https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-envvarvalue).

THank you all. That is absolutely the limitation of build script today. Configuration is the current way to deal with that.

Sorry for not being clear. I didn't mean Cargo already support the feature described in this issue. Let me summarize: * Build script can set environment variables but only for...

> ```toml > # TODO: Remove when WebGPU is no longer an unstable > [target.'cfg(target_arch="wasm32")'.profile.dev] > rustflags = ["--cfg", "web_sys_unstable_apis"] > ``` This is not a valid key in `Cargo.toml`....

Depends on how you use profile. For now we can leverage `--config ` without waiting for such feature being implemented. BTW I feel like this has been brought up, but...

@kamulos if config-include supports optional config.toml, that could be an approach to manage multiple config files. See .

If you had read it carefully, in the doc, it is under the section of ["Environment variables Cargo **_reads_**"](https://doc.rust-lang.org/cargo/reference/environment-variables.html#environment-variables-cargo-reads), which is different from the latter section ["Environment variables Cargo **_sets_**...