Add ids to all glossary items, make existing glossary links point to glossary, add links for def id in query.md

Author: Nashenas88

src/appendix/glossary.md

@@ -53,7 +53,7 @@ The monomorphization collector is run just before MIR lowering and codegen.
 [`rustc_codegen_ssa::base::codegen_crate`][codegen1] calls the
 [`collect_and_partition_mono_items`][mono] query, which does monomorphization
 collection and then partitions them into [codegen
-units](../appendix/glossary.md).
+units](../appendix/glossary.md#codegen-unit).
 
 [mono]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir/monomorphize/partitioning/fn.collect_and_partition_mono_items.html
 [codegen1]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_codegen_ssa/base/fn.codegen_crate.html

src/backend/monomorph.md

@@ -37,8 +37,8 @@ the [`mir_borrowck`] query.
   we will modify this copy in place to modify the types and things to
   include references to the new regions that we are computing.
 - We then invoke [`replace_regions_in_mir`] to modify our local MIR.
-  Among other things, this function will replace all of the [regions](./appendix/glossary.md) in
-  the MIR with fresh [inference variables](./appendix/glossary.md).
+  Among other things, this function will replace all of the [regions](./appendix/glossary.md#region) in
+  the MIR with fresh [inference variables](./appendix/glossary.md#inf-var).
 - Next, we perform a number of
   [dataflow analyses](./appendix/background.md#dataflow) that
   compute what data is moved and when.

src/borrow_check.md

@@ -55,7 +55,7 @@ includes a region R is live at some [point] P. This simply means that
 the value of R must include the point P. Liveness constraints are
 computed by the MIR type checker.
 
-[point]: ../../appendix/glossary.md
+[point]: ../../appendix/glossary.md#point
 
 A liveness constraint `R live at E` is satisfied if `E` is a member of
 `Values(R)`. So to "apply" such a constraint to `Values`, we just have

src/borrow_check/region_inference/constraint_propagation.md

@@ -53,7 +53,7 @@ the MIR).
 
 **The TL;DR is that you might get weird behavior from a compile when
 using `--keep-stage 1`** -- for example, strange
-[ICEs](../appendix/glossary.html) or other panics. In that case, you
+[ICEs](../appendix/glossary.html#ice) or other panics. In that case, you
 should simply remove the `--keep-stage 1` from the command and
 rebuild.  That ought to fix the problem.
 

src/building/suggested.md

@@ -256,4 +256,4 @@ but [you can read about those below](#promoted)).
 [mir]: https://github.com/rust-lang/rust/tree/master/src/librustc_middle/mir
 [mirmanip]: https://github.com/rust-lang/rust/tree/master/src/librustc_mir
 [mir]: https://github.com/rust-lang/rust/tree/master/src/librustc_middle/mir
-[newtype'd]: ../appendix/glossary.html
+[newtype'd]: ../appendix/glossary.html#newtype

src/mir/index.md

@@ -9,7 +9,7 @@ effective; we can optimize the generic version, so all of the monomorphizations
 are cheaper!
 
 [mir]: https://rustc-dev-guide.rust-lang.org/mir/index.html
-[monomorph]: https://rustc-dev-guide.rust-lang.org/appendix/glossary.html?highlight=monomorphize#appendix-c-glossary
+[monomorph]: https://rustc-dev-guide.rust-lang.org/appendix/glossary.html#mono
 
 MIR optimizations run after borrow checking. We run a series of optimization
 passes over the MIR to improve it. Some passes are required to run on all code,
@@ -23,7 +23,7 @@ optimizes it, and returns the improved MIR.
 
 [optmir]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir/transform/fn.optimized_mir.html
 [query]: https://rustc-dev-guide.rust-lang.org/query.html
-[defid]: https://rustc-dev-guide.rust-lang.org/appendix/glossary.html?highlight=DefId#appendix-c-glossary
+[defid]: https://rustc-dev-guide.rust-lang.org/appendix/glossary.html#def-id
 [steal]: https://rustc-dev-guide.rust-lang.org/mir/passes.html?highlight=steal#stealing
 
 ## Defining optimization passes

src/mir/optimizations.md

@@ -6,9 +6,10 @@ setup to a "demand-driven" system. **The Compiler Query System is the
 key to our new demand-driven organization.** The idea is pretty
 simple. You have various queries that compute things about the input
 – for example, there is a query called `type_of(def_id)` that, given
-the def-id of some item, will compute the type of that item and return
+the [def-id] of some item, will compute the type of that item and return
 it to you.
 
+[def-id]: appendix/glossary.md#def-id
 [hl]: high-level-overview.html
 
 Query execution is **memoized** – so the first time you invoke a

src/query.md

@@ -41,7 +41,7 @@ subtyping, we recommend you read the paper). There are a few parts:
 3. Check for _placeholder leaks_.
 
 [hrsubtype]: ./hrtb.md
-[placeholder]: ../appendix/glossary.html#appendix-c-glossary
+[placeholder]: ../appendix/glossary.html#placeholder
 [paper by SPJ]: http://research.microsoft.com/en-us/um/people/simonpj/papers/higher-rank/
 
 So let's work through our example.