compiletest: more consistent handling of bool-like env vars #125895
Labels
A-compiletest
Area: The compiletest test runner
C-cleanup
Category: PRs that clean code up or issues documenting cleanup.
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
E-medium
Call for participation: Medium difficulty. Experience needed to fix: Intermediate.
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Noticed in #125890 (comment).
It would be nice to have more consistent handling of what is considered "truthy" or "falsey" for env vars that accept a bool-ish value. In particular, if an env var's value contains invalid UTF-8, we probably should straight up error instead of silently parsing it as truthy/falsey?
The text was updated successfully, but these errors were encountered: