Add toc markers

Author: igaray

src/backend/backend-agnostic.md

@@ -1,5 +1,7 @@
 # Backend Agnostic Codegen
 
+<!-- toc -->
+
 As of January 2021, `rustc_codegen_ssa` provides an abstract interface for all backends to
 implement, to allow other codegen backends (e.g. [Cranelift]).
 

src/backend/implicit-caller-location.md

@@ -1,5 +1,7 @@
 # Implicit Caller Location
 
+<!-- toc -->
+
 Approved in [RFC 2091], this feature enables the accurate reporting of caller location during panics
 initiated from functions like `Option::unwrap`, `Result::expect`, and `Index::index`. This feature 
 adds the [`#[track_caller]`][attr-reference] attribute for functions, the 

src/backend/monomorph.md

@@ -1,5 +1,7 @@
 # Monomorphization
 
+<!-- toc -->
+
 As you probably know, rust has a very expressive type system that has extensive
 support for generic types. But of course, assembly is not generic, so we need
 to figure out the concrete types of all the generics before the code can

src/backend/updating-llvm.md

@@ -1,5 +1,7 @@
 # Updating LLVM
 
+<!-- toc -->
+
 The Rust compiler uses LLVM as its primary codegen backend today, and naturally
 we want to at least occasionally update this dependency! Currently we do not
 have a strict policy about when to update LLVM or what it can be updated to, but

src/borrow_check/moves_and_initialization/move_paths.md

@@ -1,5 +1,7 @@
 # Move paths
 
+<!-- toc -->
+
 In reality, it's not enough to track initialization at the granularity
 of local variables. Rust also allows us to do moves and initialization
 at the field granularity:

src/borrow_check/region_inference.md

@@ -1,5 +1,7 @@
 # Region inference (NLL)
 
+<!-- toc -->
+
 The MIR-based region checking code is located in [the `rustc_mir::borrow_check`
 module][nll].
 

src/borrow_check/region_inference/constraint_propagation.md

@@ -1,5 +1,7 @@
 # Constraint propagation
 
+<!-- toc -->
+
 The main work of the region inference is **constraint propagation**,
 which is done in the [`propagate_constraints`] function.  There are
 three sorts of constraints that are used in NLL, and we'll explain how

src/borrow_check/region_inference/lifetime_parameters.md

@@ -1,5 +1,7 @@
 # Universal regions
 
+<!-- toc -->
+
 "Universal regions" is the name that the code uses to refer to "named
 lifetimes" -- e.g., lifetime parameters and `'static`. The name
 derives from the fact that such lifetimes are "universally quantified"

src/borrow_check/region_inference/member_constraints.md

@@ -1,5 +1,7 @@
 # Member constraints
 
+<!-- toc -->
+
 A member constraint `'m member of ['c_1..'c_N]` expresses that the
 region `'m` must be *equal* to some **choice regions** `'c_i` (for
 some `i`). These constraints cannot be expressed by users, but they

src/borrow_check/region_inference/placeholders_and_universes.md

@@ -1,5 +1,7 @@
 # Placeholders and universes
 
+<!-- toc -->
+
 From time to time we have to reason about regions that we can't
 concretely know. For example, consider this program: