214cd1f228
Don't abort compilation after giving a lint error The only reason to use `abort_if_errors` is when the program is so broken that either: 1. later passes get confused and ICE 2. any diagnostics from later passes would be noise This is never the case for lints, because the compiler has to be able to deal with `allow`-ed lints. So it can continue to lint and compile even if there are lint errors. Closes https://github.com/rust-lang/rust/issues/82761. This is a WIP because I have a feeling it will exit with 0 even if there were lint errors; I don't have a computer that can build rustc locally at the moment. |
||
|---|---|---|
| .. | ||
| rpath | ||
| archive.rs | ||
| command.rs | ||
| link.rs | ||
| linker.rs | ||
| lto.rs | ||
| metadata.rs | ||
| mod.rs | ||
| rpath.rs | ||
| symbol_export.rs | ||
| write.rs | ||