diff options
| author | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-01-09 12:28:45 +1100 |
|---|---|---|
| committer | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-01-11 07:56:17 +1100 |
| commit | 192c4a0cf40adc752daa4fa37ca85300fbe70ab4 (patch) | |
| tree | fd848b6fb73eb9981bc9abd12e9fb890a7ff191d /tests/codegen/patchable-function-entry | |
| parent | 141b31a23f4832017e6f5ce1f58ccc1e19868e12 (diff) | |
| download | rust-192c4a0cf40adc752daa4fa37ca85300fbe70ab4.tar.gz rust-192c4a0cf40adc752daa4fa37ca85300fbe70ab4.zip | |
Change how `force-warn` lint diagnostics are recorded.
`is_force_warn` is only possible for diagnostics with `Level::Warning`, but it is currently stored in `Diagnostic::code`, which every diagnostic has. This commit: - removes the boolean `DiagnosticId::Lint::is_force_warn` field; - adds a `ForceWarning` variant to `Level`. Benefits: - The common `Level::Warning` case now has no arguments, replacing lots of `Warning(None)` occurrences. - `rustc_session::lint::Level` and `rustc_errors::Level` are more similar, both having `ForceWarning` and `Warning`.
Diffstat (limited to 'tests/codegen/patchable-function-entry')
0 files changed, 0 insertions, 0 deletions