diff options
| author | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-05-09 18:44:40 +1000 |
|---|---|---|
| committer | Nicholas Nethercote <n.nethercote@gmail.com> | 2024-05-09 20:12:07 +1000 |
| commit | fd91925bce5f443bf963042f1ebaf0b3330212fe (patch) | |
| tree | a0dacae5183ec626d89536efa1ebed7d08aae9b9 /compiler/rustc_codegen_llvm/src/errors.rs | |
| parent | 87293c9585a7fb2cc83ca9949ae79661d5d3c31a (diff) | |
| download | rust-fd91925bce5f443bf963042f1ebaf0b3330212fe.tar.gz rust-fd91925bce5f443bf963042f1ebaf0b3330212fe.zip | |
Add `ErrorGuaranteed` to `Recovered::Yes` and use it more.
The starting point for this was identical comments on two different
fields, in `ast::VariantData::Struct` and `hir::VariantData::Struct`:
```
// FIXME: investigate making this a `Option<ErrorGuaranteed>`
recovered: bool
```
I tried that, and then found that I needed to add an `ErrorGuaranteed`
to `Recovered::Yes`. Then I ended up using `Recovered` instead of
`Option<ErrorGuaranteed>` for these two places and elsewhere, which
required moving `ErrorGuaranteed` from `rustc_parse` to `rustc_ast`.
This makes things more consistent, because `Recovered` is used in more
places, and there are fewer uses of `bool` and
`Option<ErrorGuaranteed>`. And safer, because it's difficult/impossible
to set `recovered` to `Recovered::Yes` without having emitted an error.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/errors.rs')
0 files changed, 0 insertions, 0 deletions
