Fix some broken fragment links.

This commit is contained in:
Eric Huss 2019-11-05 09:20:45 -08:00 committed by Who? Me?!
parent fbe5ef0f93
commit 27f0854e6c
3 changed files with 3 additions and 3 deletions

View File

@ -61,7 +61,7 @@ rib | a data structure in the name resolver that keeps trac
sess | the compiler session, which stores global data used throughout compilation sess | the compiler session, which stores global data used throughout compilation
side tables | because the AST and HIR are immutable once created, we often carry extra information about them in the form of hashtables, indexed by the id of a particular node. side tables | because the AST and HIR are immutable once created, we often carry extra information about them in the form of hashtables, indexed by the id of a particular node.
sigil | like a keyword but composed entirely of non-alphanumeric tokens. For example, `&` is a sigil for references. sigil | like a keyword but composed entirely of non-alphanumeric tokens. For example, `&` is a sigil for references.
placeholder | **NOTE: skolemization is deprecated by placeholder** a way of handling subtyping around "for-all" types (e.g., `for<'a> fn(&'a u32)`) as well as solving higher-ranked trait bounds (e.g., `for<'a> T: Trait<'a>`). See [the chapter on placeholder and universes](../borrow_check/region_inference.html#placeholders-and-universes) for more details. placeholder | **NOTE: skolemization is deprecated by placeholder** a way of handling subtyping around "for-all" types (e.g., `for<'a> fn(&'a u32)`) as well as solving higher-ranked trait bounds (e.g., `for<'a> T: Trait<'a>`). See [the chapter on placeholder and universes](../borrow_check/region_inference/placeholders_and_universes.md) for more details.
soundness | soundness is a technical term in type theory. Roughly, if a type system is sound, then if a program type-checks, it is type-safe; i.e. I can never (in safe rust) force a value into a variable of the wrong type. (see "completeness"). soundness | soundness is a technical term in type theory. Roughly, if a type system is sound, then if a program type-checks, it is type-safe; i.e. I can never (in safe rust) force a value into a variable of the wrong type. (see "completeness").
span | a location in the user's source code, used for error reporting primarily. These are like a file-name/line-number/column tuple on steroids: they carry a start/end point, and also track macro expansions and compiler desugaring. All while being packed into a few bytes (really, it's an index into a table). See the Span datatype for more. span | a location in the user's source code, used for error reporting primarily. These are like a file-name/line-number/column tuple on steroids: they carry a start/end point, and also track macro expansions and compiler desugaring. All while being packed into a few bytes (really, it's an index into a table). See the Span datatype for more.
substs | the substitutions for a given generic type or item (e.g. the `i32`, `u32` in `HashMap<i32, u32>`) substs | the substitutions for a given generic type or item (e.g. the `i32`, `u32` in `HashMap<i32, u32>`)

View File

@ -100,7 +100,7 @@ The kinds of region elements are as follows:
- There is an element `!1` for each placeholder region `!1`. This - There is an element `!1` for each placeholder region `!1`. This
corresponds (intuitively) to some unknown set of other elements corresponds (intuitively) to some unknown set of other elements
for details on placeholders, see the section for details on placeholders, see the section
[placeholders and universes](#placeholder). [placeholders and universes](region_inference/placeholders_and_universes.md).
## Constraints ## Constraints

View File

@ -5,7 +5,7 @@ by the build system (`x.py test`). The main test harness for testing
the compiler itself is a tool called compiletest (sources in the the compiler itself is a tool called compiletest (sources in the
[`src/tools/compiletest`]). This section gives a brief overview of how [`src/tools/compiletest`]). This section gives a brief overview of how
the testing framework is setup, and then gets into some of the details the testing framework is setup, and then gets into some of the details
on [how to run tests](./running.html#ui) as well as on [how to run tests](./running.html) as well as
[how to add new tests](./adding.html). [how to add new tests](./adding.html).
[`src/tools/compiletest`]: https://github.com/rust-lang/rust/tree/master/src/tools/compiletest [`src/tools/compiletest`]: https://github.com/rust-lang/rust/tree/master/src/tools/compiletest