about summary refs log tree commit diff
diff options
context:
space:
mode:
authorStan Manilov <stanislav.manilov@gmail.com>2025-04-29 16:39:54 +0300
committerGitHub <noreply@github.com>2025-04-29 16:39:54 +0300
commitc466cd01d8b6fdac7c506bad2b035df653bfd921 (patch)
tree7e382067a29b88af12dc2088a84945d1a4feddd1
parent5ce6fa79d09beecdbeadd1f08c605bb904f7b65b (diff)
downloadrust-c466cd01d8b6fdac7c506bad2b035df653bfd921.tar.gz
rust-c466cd01d8b6fdac7c506bad2b035df653bfd921.zip
Update compiler-src.md
Refactor the dependency structure from a nested unordered list to a single-level ordered list.

IMO, this is clearer, but happy to close this PR without merging, if the change is not desired.
-rw-r--r--src/doc/rustc-dev-guide/src/compiler-src.md25
1 files changed, 12 insertions, 13 deletions
diff --git a/src/doc/rustc-dev-guide/src/compiler-src.md b/src/doc/rustc-dev-guide/src/compiler-src.md
index c538fc8b788..0d3cbebb4da 100644
--- a/src/doc/rustc-dev-guide/src/compiler-src.md
+++ b/src/doc/rustc-dev-guide/src/compiler-src.md
@@ -62,21 +62,20 @@ huge. There is also the `rustc` crate which is the actual binary (i.e. the
 [`rustc_driver`] crate, which drives the various parts of compilation in other
 crates.
 
-The dependency structure of these crates is complex, but roughly it is
+The dependency order of these crates is complex, but roughly it is
 something like this:
 
-- `rustc` (the binary) calls [`rustc_driver::main`][main].
-    - [`rustc_driver`] depends on a lot of other crates, but the main one is
-      [`rustc_interface`].
-        - [`rustc_interface`] depends on most of the other compiler crates. It
-          is a fairly generic interface for driving the whole compilation.
-            - Most of the other `rustc_*` crates depend on [`rustc_middle`],
-              which defines a lot of central data structures in the compiler.
-                - [`rustc_middle`] and most of the other crates depend on a
-                  handful of crates representing the early parts of the
-                  compiler (e.g. the parser), fundamental data structures (e.g.
-                  [`Span`]), or error reporting: [`rustc_data_structures`],
-                  [`rustc_span`], [`rustc_errors`], etc.
+1. `rustc` (the binary) calls [`rustc_driver::main`][main].
+1. [`rustc_driver`] depends on a lot of other crates, but the main one is
+   [`rustc_interface`].
+1. [`rustc_interface`] depends on most of the other compiler crates. It is a
+   fairly generic interface for driving the whole compilation.
+1. Most of the other `rustc_*` crates depend on [`rustc_middle`], which defines
+   a lot of central data structures in the compiler.
+1. [`rustc_middle`] and most of the other crates depend on a handful of crates
+   representing the early parts of the compiler (e.g. the parser), fundamental
+   data structures (e.g. [`Span`]), or error reporting:
+   [`rustc_data_structures`], [`rustc_span`], [`rustc_errors`], etc.
 
 [`rustc_data_structures`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_data_structures/index.html
 [`rustc_driver`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_driver/index.html