sembr src/diagnostics/error-codes.md

Author: tshepang

src/diagnostics/error-codes.md

@@ -1,24 +1,24 @@
 # Error codes
-We generally try to assign each error message a unique code like `E0123`. These
-codes are defined in the compiler in the `diagnostics.rs` files found in each
-crate, which basically consist of macros. All error codes have an associated
-explanation: new error codes must include them. Note that not all _historical_
-(no longer emitted) error codes have explanations.
+We generally try to assign each error message a unique code like `E0123`.
+These codes are defined in the compiler in the `diagnostics.rs` files found in each
+crate, which basically consist of macros.
+All error codes have an associated explanation: new error codes must include them.
+Note that not all _historical_ (no longer emitted) error codes have explanations.
 
 ## Error explanations
 
 The explanations are written in Markdown (see the [CommonMark Spec] for
-specifics around syntax), and all of them are linked in the [`rustc_error_codes`]
-crate. Please read [RFC 1567] for details on how to format and write long error
-codes. As of <!-- date-check --> February 2023, there is an
-effort[^new-explanations] to replace this largely outdated RFC with a new more
-flexible standard.
+specifics around syntax), and all of them are linked in the [`rustc_error_codes`] crate.
+Please read [RFC 1567] for details on how to format and write long error codes.
+As of <!-- date-check --> February 2023, there is an
+effort[^new-explanations] to replace this largely outdated RFC with a new more flexible standard.
 
 Error explanations should expand on the error message and provide details about
-_why_ the error occurs. It is not helpful for users to copy-paste a quick fix;
-explanations should help users understand why their code cannot be accepted by
-the compiler. Rust prides itself on helpful error messages and long-form
-explanations are no exception. However, before error explanations are
+_why_ the error occurs.
+It is not helpful for users to copy-paste a quick fix;
+explanations should help users understand why their code cannot be accepted by the compiler.
+Rust prides itself on helpful error messages and long-form explanations are no exception.
+However, before error explanations are
 overhauled[^new-explanations] it is a bit open as to how exactly they should be
 written, as always: ask your reviewer or ask around on the Rust Zulip.
 
@@ -33,12 +33,12 @@ written, as always: ask your reviewer or ask around on the Rust Zulip.
 
 Error codes are stored in `compiler/rustc_error_codes`.
 
-To create a new error, you first need to find the next available code. 
+To create a new error, you first need to find the next available code.
 You can find it by opening `rustc_error_codes/src/lib.rs` and scrolling down 
 to the end of the `error_codes!` macro declaration.
 
-Here we might see the highest error code in use is `E0805`, so we _probably_ want
-`E0806`. To be sure, run `rg E0806` and check, you should see no references.
+Here we might see the highest error code in use is `E0805`, so we _probably_ want `E0806`.
+To be sure, run `rg E0806` and check, you should see no references.
 
 You will have to write an extended description for your error,
 which will go in `rustc_error_codes/src/error_codes/E0806.md`.
@@ -62,8 +62,7 @@ struct_span_code_err!(self.dcx(), // some path to the `DiagCtxt` here
     .emit() // actually issue the error
 ```
 
-If you want to add notes or other snippets, you can invoke methods before you
-call `.emit()`:
+If you want to add notes or other snippets, you can invoke methods before you call `.emit()`:
 
 ```rust
 struct_span_code_err!(...)