add coercions chapter and split out non hir typeck stuff

Author: BoxyUwU

src/SUMMARY.md

@@ -186,14 +186,15 @@
         - [Opaque types](./solve/opaque-types.md)
         - [Significant changes and quirks](./solve/significant-changes.md)
     - [`Unsize` and `CoerceUnsized` traits](./traits/unsize.md)
-- [Type checking](./type-checking.md)
-    - [Method lookup](./method-lookup.md)
-    - [Variance](./variance.md)
-    - [Coherence checking](./coherence.md)
-    - [Opaque types](./opaque-types-type-alias-impl-trait.md)
-        - [Inference details](./opaque-types-impl-trait-inference.md)
-        - [Return Position Impl Trait In Trait](./return-position-impl-trait-in-trait.md)
-        - [Region inference restrictions][opaque-infer]
+- [Variance](./variance.md)
+- [Coherence checking](./coherence.md)
+- [HIR Type checking](./hir-typeck/summary.md)
+    - [Coercions](./hir-typeck/coercions.md)
+    - [Method lookup](./hir-typeck/method-lookup.md)
+- [Opaque types](./opaque-types-type-alias-impl-trait.md)
+    - [Inference details](./opaque-types-impl-trait-inference.md)
+    - [Return Position Impl Trait In Trait](./return-position-impl-trait-in-trait.md)
+    - [Region inference restrictions][opaque-infer]
 - [Const condition checking](./effects.md)
 - [Pattern and exhaustiveness checking](./pat-exhaustive-checking.md)
 - [Unsafety checking](./unsafety-checking.md)

src/appendix/code-index.md

@@ -33,7 +33,7 @@ Item            |  Kind    | Short description           | Chapter            |
 [Identifiers in the HIR]: ../hir.html#hir-id
 [The parser]: ../the-parser.html
 [The Rustc Driver and Interface]: ../rustc-driver/intro.html
-[Type checking]: ../type-checking.html
+[Type checking]: ../hir-typeck/summary.html
 [The `ty` modules]: ../ty.html
 [Rustdoc]: ../rustdoc.html
 [Emitting Diagnostics]: ../diagnostics.html

src/appendix/glossary.md

@@ -88,7 +88,7 @@ Term                                                  | Meaning
 <span id="trans">trans</span>                  |  Short for _translation_, the code to translate MIR into LLVM IR. Renamed to [codegen](#codegen).
 <span id="ty">`Ty`</span>                      |  The internal representation of a type. ([see more](../ty.md))
 <span id="tyctxt">`TyCtxt`</span>              |  The data structure often referred to as [`tcx`](#tcx) in code which provides access to session data and the query system.
-<span id="ufcs">UFCS</span>                    |  Short for _universal function call syntax_, this is an unambiguous syntax for calling a method. **Term no longer in use!** Prefer _fully-qualified path/syntax_. ([see more](../type-checking.md), [see the reference](https://doc.rust-lang.org/reference/expressions/call-expr.html#disambiguating-function-calls))
+<span id="ufcs">UFCS</span>                    |  Short for _universal function call syntax_, this is an unambiguous syntax for calling a method. **Term no longer in use!** Prefer _fully-qualified path/syntax_. ([see more](../hir-typeck/summary.md), [see the reference](https://doc.rust-lang.org/reference/expressions/call-expr.html#disambiguating-function-calls))
 <span id="ut">uninhabited type</span>          |  A type which has _no_ values. This is not the same as a ZST, which has exactly 1 value. An example of an uninhabited type is `enum Foo {}`, which has no variants, and so, can never be created. The compiler can treat code that deals with uninhabited types as dead code, since there is no such value to be manipulated. `!` (the never type) is an uninhabited type. Uninhabited types are also called _empty types_.
 <span id="upvar">upvar</span>                  |  A variable captured by a closure from outside the closure.
 <span id="variance">variance</span>            |  Determines how changes to a generic parameter affect subtyping; for example, if `T` is a subtype of `U`, then `Vec<T>` is a subtype `Vec<U>` because `Vec` is _covariant_ in its generic parameter. See [the background chapter](./background.md#variance) for a more general explanation. See the [variance chapter](../variance.md) for an explanation of how type checking handles variance.

src/hir-typeck/coercions.md

@@ -1,4 +1,4 @@
-# Type checking
+# HIR Type checking
 
 The [`hir_analysis`] crate contains the source for "type collection" as well
 as a bunch of related functionality.
@@ -7,8 +7,8 @@ These crates draw heavily on the [type inference] and [trait solving].
 
 [`hir_analysis`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir_analysis/index.html
 [`hir_typeck`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir_typeck/index.html
-[type inference]: ./type-inference.md
-[trait solving]: ./traits/resolution.md
+[type inference]: ./../type-inference.md
+[trait solving]: ./../traits/resolution.md
 
 ## Type collection
 
@@ -40,7 +40,7 @@ type *checking*).
 
 For more details, see the [`collect`][collect] module.
 
-[queries]: ./query.md
+[queries]: ../query.md
 [collect]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_hir_analysis/collect/index.html
 
 **TODO**: actually talk about type checking... [#1161](https://github.com/rust-lang/rustc-dev-guide/issues/1161)

src/method-lookup.md renamed to src/hir-typeck/method-lookup.md

@@ -130,7 +130,7 @@ with additional low-level types and annotations added (e.g. an ELF object or
 the final binary.
 
 [*trait solving*]: traits/resolution.md
-[*type checking*]: type-checking.md
+[*type checking*]: hir-typeck/summary.md
 [*type inference*]: type-inference.md
 [`bump`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_parse/parser/struct.Parser.html#method.bump
 [`check`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_parse/parser/struct.Parser.html#method.check

src/type-checking.md renamed to src/hir-typeck/summary.md

@@ -5,7 +5,7 @@ The THIR ("Typed High-Level Intermediate Representation"), previously called HAI
 [type checking]. It is (as of <!-- date-check --> January 2024) used for
 [MIR construction], [exhaustiveness checking], and [unsafety checking].
 
-[type checking]: ./type-checking.md
+[type checking]: ./hir-typeck/summary.md
 [MIR construction]: ./mir/construction.md
 [exhaustiveness checking]: ./pat-exhaustive-checking.md
 [unsafety checking]: ./unsafety-checking.md

src/overview.md

@@ -214,7 +214,7 @@ As a result of this assignment, the type of `u` is forced to be
 `Option<Vec<?V>>`, where `?V` represents the element type of the
 vector. This in turn implies that `?U` is [unified] to `Vec<?V>`.
 
-[unified]: ../type-checking.html
+[unified]: ../hir-typeck/summary.md
 
 Let's suppose that the type checker decides to revisit the
 "as-yet-unproven" trait obligation we saw before, `Vec<?T>: