diff options
| author | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-01-13 13:11:56 +1100 |
|---|---|---|
| committer | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-01-14 14:04:25 +1100 |
| commit | d71f535a6f39e82313b46ac3157c4ed9267a2e40 (patch) | |
| tree | 4cbb2745d2572c11bba4f59173552356df7460f5 /tests/rustdoc-js-std/osstring-to-string.js | |
| parent | 2de99ec787c80d4ba5ac4638d371a5bd8b752795 (diff) | |
| download | rust-d71f535a6f39e82313b46ac3157c4ed9267a2e40.tar.gz rust-d71f535a6f39e82313b46ac3157c4ed9267a2e40.zip | |
Rework how diagnostic lints are stored.
`Diagnostic::code` has the type `DiagnosticId`, which has `Error` and `Lint` variants. Plus `Diagnostic::is_lint` is a bool, which should be redundant w.r.t. `Diagnostic::code`. Seems simple. Except it's possible for a lint to have an error code, in which case its `code` field is recorded as `Error`, and `is_lint` is required to indicate that it's a lint. This is what happens with `derive(LintDiagnostic)` lints. Which means those lints don't have a lint name or a `has_future_breakage` field because those are stored in the `DiagnosticId::Lint`. It's all a bit messy and confused and seems unintentional. This commit: - removes `DiagnosticId`; - changes `Diagnostic::code` to `Option<String>`, which means both errors and lints can straightforwardly have an error code; - changes `Diagnostic::is_lint` to `Option<IsLint>`, where `IsLint` is a new type containing a lint name and a `has_future_breakage` bool, so all lints can have those, error code or not.
Diffstat (limited to 'tests/rustdoc-js-std/osstring-to-string.js')
0 files changed, 0 insertions, 0 deletions
