Fix existing messages in the diag structs

Author: JonathanBrouwer

compiler/rustc_codegen_llvm/src/errors.rs

@@ -214,5 +214,5 @@ pub(crate) struct FixedX18InvalidArch<'a> {
 }
 
 #[derive(Diagnostic)]
-#[diag("`-Zsanitizer-kcfi-arity` requires LLVM 21.0.0 or later.")]
+#[diag("`-Zsanitizer-kcfi-arity` requires LLVM 21.0.0 or later")]
 pub(crate) struct SanitizerKcfiArityRequiresLLVM2100;

compiler/rustc_codegen_ssa/src/errors.rs

@@ -59,7 +59,7 @@ pub(crate) struct MissingQueryDepGraph {
 
 #[derive(Diagnostic)]
 #[diag(
-    "found malformed codegen unit name `{$user_path}`. codegen units names must always start with the name of the crate (`{$crate_name}` in this case)."
+    "found malformed codegen unit name `{$user_path}`. codegen units names must always start with the name of the crate (`{$crate_name}` in this case)"
 )]
 pub(crate) struct MalformedCguName {
     #[primary_span]
@@ -562,12 +562,12 @@ pub(crate) struct SelfContainedLinkerMissing;
 
 #[derive(Diagnostic)]
 #[diag(
-    "please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option."
+    "please ensure that Visual Studio 2017 or later, or Build Tools for Visual Studio were installed with the Visual C++ option"
 )]
 pub(crate) struct CheckInstalledVisualStudio;
 
 #[derive(Diagnostic)]
-#[diag("VS Code is a different product, and is not sufficient.")]
+#[diag("VS Code is a different product, and is not sufficient")]
 pub(crate) struct InsufficientVSCodeProduct;
 
 #[derive(Diagnostic)]
@@ -610,13 +610,13 @@ pub(crate) struct LinkerFileStem;
 
 #[derive(Diagnostic)]
 #[diag(
-    "link against the following native artifacts when linking against this static library. The order and any duplication can be significant on some platforms."
+    "link against the following native artifacts when linking against this static library. The order and any duplication can be significant on some platforms"
 )]
 pub(crate) struct StaticLibraryNativeArtifacts;
 
 #[derive(Diagnostic)]
 #[diag(
-    "native artifacts to link against have been written to {$path}. The order and any duplication can be significant on some platforms."
+    "native artifacts to link against have been written to {$path}. The order and any duplication can be significant on some platforms"
 )]
 pub(crate) struct StaticLibraryNativeArtifactsToFile<'a> {
     pub path: &'a Path,

compiler/rustc_driver_impl/src/session_diagnostics.rs

@@ -51,7 +51,7 @@ pub(crate) struct RlinkCorruptFile<'a> {
 }
 
 #[derive(Diagnostic)]
-#[diag("the compiler unexpectedly panicked. this is a bug.")]
+#[diag("the compiler unexpectedly panicked. This is a bug")]
 pub(crate) struct Ice;
 
 #[derive(Diagnostic)]

compiler/rustc_hir_typeck/src/errors.rs

@@ -1145,7 +1145,7 @@ pub(crate) struct CastThinPointerToWidePointer<'tcx> {
     pub expr_ty: Ty<'tcx>,
     pub cast_ty: Ty<'tcx>,
     #[note(
-        "Thin pointers are \"simple\" pointers: they are purely a reference to a
+        "thin pointers are \"simple\" pointers: they are purely a reference to a
         memory address.
 
         Wide pointers are pointers referencing \"Dynamically Sized Types\" (also

compiler/rustc_incremental/src/errors.rs

@@ -281,7 +281,7 @@ pub(crate) struct DeleteWorkProduct<'a> {
 
 #[derive(Diagnostic)]
 #[diag(
-    "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."
+    "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"
 )]
 pub(crate) struct CorruptFile<'a> {
     pub path: &'a Path,