diff --git a/src/appendix/background.md b/src/appendix/background.md index fd73ee064..d36927e82 100644 --- a/src/appendix/background.md +++ b/src/appendix/background.md @@ -4,7 +4,7 @@ This section covers a numbers of common compiler terms that arise in this guide. We try to give the general definition while providing some Rust-specific context. - + ## What is a control-flow graph? @@ -100,7 +100,7 @@ When using a control-flow graph, a loop simply appears as a cycle in the graph, and the `break` keyword translates into a path out of that cycle. - + ## What is a dataflow analysis? @@ -186,7 +186,7 @@ useful. For example, rather than starting from block (A) and moving forwards, we might have started with the usage of `x` and moved backwards to try to find its initialization. - + ## What is "universally quantified"? What about "existentially quantified"? @@ -233,7 +233,7 @@ fn foo(_: dyn Debug) This function claims that there exists some type `T` that implements `Debug` such that the function is well-typed: `∃ T: (T: Debug) and well_typed(foo)`. - + ## What is a de Bruijn Index? @@ -268,7 +268,7 @@ Check out the subtyping chapter from the See the [variance](../variance.html) chapter of this guide for more info on how the type checker handles variance. - + ## What is a "free region" or a "free variable"? What about "bound region"? diff --git a/src/borrow_check/region_inference.md b/src/borrow_check/region_inference.md index 5d06d8dd4..85e71b4fa 100644 --- a/src/borrow_check/region_inference.md +++ b/src/borrow_check/region_inference.md @@ -70,7 +70,7 @@ TODO: write about _how_ these regions are computed. [`UniversalRegions`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_borrowck/universal_regions/struct.UniversalRegions.html - + ## Region variables diff --git a/src/borrow_check/region_inference/member_constraints.md b/src/borrow_check/region_inference/member_constraints.md index e236e0124..fd7c87ffc 100644 --- a/src/borrow_check/region_inference/member_constraints.md +++ b/src/borrow_check/region_inference/member_constraints.md @@ -171,7 +171,7 @@ This choice is consistent with the general 'flow' of region propagation, which always aims to compute a minimal value for the region being inferred. However, it is somewhat arbitrary. - + ### Collecting upper bounds in the implementation diff --git a/src/bug-fix-procedure.md b/src/bug-fix-procedure.md index ba76ec06e..4857cf5e0 100644 --- a/src/bug-fix-procedure.md +++ b/src/bug-fix-procedure.md @@ -227,7 +227,7 @@ that we use for unstable features: Ideally, breaking changes should have landed on the **stable branch** of the compiler before they are finalized. - + ### Removing a lint diff --git a/src/conventions.md b/src/conventions.md index e7a8d00cc..37af8121c 100644 --- a/src/conventions.md +++ b/src/conventions.md @@ -3,7 +3,7 @@ chapter covers [formatting](#formatting), [coding for correctness](#cc), [using crates from crates.io](#cio), and some tips on [structuring your PR for easy review](#er). - + # Formatting and the tidy script @@ -40,7 +40,7 @@ When modifying that code, use this command to format it: This uses a pinned version of `clang-format`, to avoid relying on the local environment. - + @@ -71,7 +71,7 @@ that case, you can add a comment towards the top of the file like so: Prefer 4-space indent. - + # Coding for correctness @@ -113,13 +113,13 @@ if foo { } ``` - + # Using crates from crates.io See the [crates.io dependencies][crates] section. - + # How to structure your PR diff --git a/src/hir.md b/src/hir.md index 8828d3da3..51893d537 100644 --- a/src/hir.md +++ b/src/hir.md @@ -74,7 +74,7 @@ the compiler a chance to observe that you accessed the data for [`&rustc_hir::Item`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir/hir/struct.Item.html - + ## Identifiers in the HIR diff --git a/src/mir/index.md b/src/mir/index.md index ef6f2f518..778c58391 100644 --- a/src/mir/index.md +++ b/src/mir/index.md @@ -325,7 +325,7 @@ As a consequence, all decoding of `ValTree` must happen by matching on the type decisions depending on that. The value itself gives no useful information without the type that belongs to it. - + ### Promoted constants diff --git a/src/notification-groups/about.md b/src/notification-groups/about.md index 77bd868d1..74629aa08 100644 --- a/src/notification-groups/about.md +++ b/src/notification-groups/about.md @@ -43,7 +43,7 @@ particularly those of **middle priority**: can accumulate over time, and the role of the notification group is to try and stop that from happening! - + ## Joining a notification group diff --git a/src/queries/incremental-compilation.md b/src/queries/incremental-compilation.md index c2c195a4a..6e5b4e8cc 100644 --- a/src/queries/incremental-compilation.md +++ b/src/queries/incremental-compilation.md @@ -92,7 +92,7 @@ Try-mark-green works as follows: - Otherwise, **all** of the nodes in `reads(Q)` must be **green**. In that case, we can color Q as **green** and return. - + ### The query DAG diff --git a/src/stabilization_guide.md b/src/stabilization_guide.md index 76da39509..f875c6874 100644 --- a/src/stabilization_guide.md +++ b/src/stabilization_guide.md @@ -13,7 +13,7 @@ following steps: ## Documentation PRs - + If any documentation for this feature exists, it should be in the [`Unstable Book`], located at [`src/doc/unstable-book`]. diff --git a/src/tests/adding.md b/src/tests/adding.md index 262bbbd7f..895eabfbd 100644 --- a/src/tests/adding.md +++ b/src/tests/adding.md @@ -180,7 +180,7 @@ if the new output makes sense. You may also need to re-bless the output with the `--bless` flag. - + ## Comment explaining what the test is about diff --git a/src/traits/canonical-queries.md b/src/traits/canonical-queries.md index 5ba450d4e..792858bd2 100644 --- a/src/traits/canonical-queries.md +++ b/src/traits/canonical-queries.md @@ -95,7 +95,7 @@ Rc: Clone After all, `Rc` is true **no matter what type `?T` is**. - + ## A trait query in rustc diff --git a/src/traits/goals-and-clauses.md b/src/traits/goals-and-clauses.md index 4315b3e0f..40fd4581b 100644 --- a/src/traits/goals-and-clauses.md +++ b/src/traits/goals-and-clauses.md @@ -47,7 +47,7 @@ In terms of code, these types are defined in [traits_mod]: https://github.com/rust-lang/rust/blob/master/compiler/rustc_middle/src/traits/mod.rs [chalk_ir]: https://github.com/rust-lang/chalk/blob/master/chalk-ir/src/lib.rs - + ## Domain goals @@ -63,7 +63,7 @@ forall { DomainGoal :- Goal } hence domain goals are in fact clauses' LHS. That is, at the most granular level, domain goals are what the trait solver will end up trying to prove. - + To define the set of domain goals in our system, we need to first introduce a few simple formulations. A **trait reference** consists of @@ -78,7 +78,7 @@ IntoIterator`. Note that Rust surface syntax also permits some extra things, like associated type bindings (`Vec: IntoIterator`), that are not part of a trait reference. - + A **projection** consists of an associated item reference along with its inputs P0..Pm: @@ -205,7 +205,7 @@ e.g. `Outlives(&'a str: 'b)`, `Outlives('a: 'static)` True if the given type or region on the left outlives the right-hand region. - + ## Coinductive goals diff --git a/src/type-inference.md b/src/type-inference.md index 4043789d0..c03fa36d7 100644 --- a/src/type-inference.md +++ b/src/type-inference.md @@ -51,7 +51,7 @@ The `tcx.infer_ctxt` method actually returns a builder, which means there are some kinds of configuration you can do before the `infcx` is created. See `InferCtxtBuilder` for more information. - + ## Inference variables diff --git a/src/variance.md b/src/variance.md index c03de7a20..ad4fa4adf 100644 --- a/src/variance.md +++ b/src/variance.md @@ -143,7 +143,7 @@ will wind up being considered green after it is re-evaluated. [rga]: ./queries/incremental-compilation.html - + ## Addendum: Variance on traits diff --git a/src/walkthrough.md b/src/walkthrough.md index ce8956957..6e07ceb7d 100644 --- a/src/walkthrough.md +++ b/src/walkthrough.md @@ -151,7 +151,7 @@ Here is the tracking issue on for our [`?` macro feature][tracking]. [tracking]: https://github.com/rust-lang/rust/issues/48075 - + ## Implementation