diff options
| author | bors <bors@rust-lang.org> | 2023-12-13 19:45:57 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-12-13 19:45:57 +0000 |
| commit | a90372c6e80cde01018b5486b27eefe66c629068 (patch) | |
| tree | 87a345aba6b0c9f40ba77147fce7ce5a3c864ee1 /compiler/rustc_pattern_analysis/src/errors.rs | |
| parent | 2862500152d89996ab2b682f22ed7e8923396992 (diff) | |
| parent | f6617d050d831cd2f1ad41a71731568a5e5e2c12 (diff) | |
| download | rust-a90372c6e80cde01018b5486b27eefe66c629068.tar.gz rust-a90372c6e80cde01018b5486b27eefe66c629068.zip | |
Auto merge of #118213 - Urgau:check-cfg-diagnostics-rustc-cargo, r=petrochenkov
Add more suggestions to unexpected cfg names and values
This pull request adds more suggestion to unexpected cfg names and values diagnostics:
- it first adds a links to the [rustc unstable book](https://doc.rust-lang.org/nightly/unstable-book/compiler-flags/check-cfg.html) or the [Cargo reference](https://doc.rust-lang.org/nightly/cargo/reference/unstable.html#check-cfg), depending if rustc is invoked by Cargo
- it secondly adds a suggestion on how to expect the cfg name or value:
*excluding well known names and values*
- for Cargo: it suggest using a feature or `cargo:rust-check-cfg` in build script
- for rustc: it suggest using `--check-cfg` (with the correct invocation)
Those diagnostics improvements are directed towards enabling users to fix the issue if the previous suggestions weren't good enough.
r? `@petrochenkov`
Diffstat (limited to 'compiler/rustc_pattern_analysis/src/errors.rs')
0 files changed, 0 insertions, 0 deletions