6 commits

Author	SHA1	Message	Date
Joshua Nelson	0ac13bd430	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.	2021-11-08 01:22:28 +00:00
Michael Woerister	af1b65cb18	Path remapping: Make behavior of diagnostics output dependent on presence of --remap-path-prefix.	2021-08-27 11:50:44 +02:00
Ryan Levick	a3d6905053	Force warnings even when can_emit_warnings == false	2021-06-30 11:18:33 +02:00
Andy Wang	5417b45c26	Use local and remapped paths where appropriate	2021-05-05 15:31:28 +01:00
Aaron Hill	23018a55d9	Implement rustc side of report-future-incompat	2020-10-30 20:02:14 -04:00
mark	9e5f7d5631	mv compiler to compiler/	2020-08-30 18:45:07 +03:00

Renamed from src/librustc_errors/annotate_snippet_emitter_writer.rs (Browse further)