You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rollup merge of rust-lang#152235 - JonathanBrouwer:convert_parse, r=JonathanBrouwer
Convert to inline diagnostics in `rustc_parse`
This was the most annoying one by far, had to make a few changes to the representation of two errors (no user-facing changes tho), these changes are in separate commits for clarity :)
For rust-lang#151366
r? @jdonszelmann
"link against the following native artifacts when linking against this static library. The order and any duplication can be significant on some platforms."
613
+
"link against the following native artifacts when linking against this static library. The order and any duplication can be significant on some platforms"
614
614
)]
615
615
pub(crate)structStaticLibraryNativeArtifacts;
616
616
617
617
#[derive(Diagnostic)]
618
618
#[diag(
619
-
"native artifacts to link against have been written to {$path}. The order and any duplication can be significant on some platforms."
619
+
"native artifacts to link against have been written to {$path}. The order and any duplication can be significant on some platforms"
"corrupt incremental compilation artifact found at `{$path}`. This file will automatically be ignored and deleted. If you see this message repeatedly or can provoke it without manually manipulating the compiler's artifacts, please file an issue. The incremental compilation system relies on hardlinks and filesystem locks behaving correctly, and may not deal well with OS crashes, so whatever information you can provide about your filesystem or other state may be very relevant."
284
+
"corrupt incremental compilation artifact found at `{$path}`. This file will automatically be ignored and deleted. If you see this message repeatedly or can provoke it without manually manipulating the compiler's artifacts, please file an issue. The incremental compilation system relies on hardlinks and filesystem locks behaving correctly, and may not deal well with OS crashes, so whatever information you can provide about your filesystem or other state may be very relevant"
0 commit comments