bazelbuild / bazelbuild/rules_cc
Why do most toolchains in this repo miss no_legacy_features?
Open
P3
- Dominant language
- Starlark
- Stars
- 247
- Forks
- 196
- PR merge metrics
- No merged PRs in 30d
Description
According to the Bazel documentation at https://bazel.build/docs/cc-toolchain-config-reference:
> [...], and for production toolchains consider adding no_legacy_features to make the toolchain more standalone.
Why is no_legacy_features only used by the Windows toolchain? Especially with the "Starlarkification" of toolchains that is going on, wouldn't it make sense to set this and make the features/action_configs on the toolchains self contained?
Contributor guide
Assessment
This issue has not been assessed yet.