Tracking Issue for warnings (config build.warnings)

[epage]

View all comments

Summary

Original issue: #8424, #14258
Implementation: #14388
Documentation: https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#warnings

Allows control over warnings via a new Cargo configuration option build.warnings.

Unresolved Issues

• What operations should this apply to and is [build] the right home for this?
• Should we turn rustc hard warnings into errors? See fix(compile): build.warnings=deny shouldn't block hard warnings #16213
• What non-rustc lints are in scope? See also Add --deny-warnings functionality for all commands. #8424 (comment)
  • Including build script warnings? See Add --deny-warnings functionality for all commands. #8424 (comment)

Future Extensions

• CLI support
  • If or where we have individual lint level control (cargo clippy), these looking odd next to each other
  • See also Add --deny-warnings functionality for all commands. #8424 (comment)
• If we add a new level, config/cli to control it

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.