From 11b83ebb5a35e3a490172903161dc99f55941024 Mon Sep 17 00:00:00 2001 From: Ryan Levick Date: Mon, 4 Jan 2021 13:55:24 +0100 Subject: [PATCH] Add link to rust-analyzer docs on getting started page --- src/getting-started.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/getting-started.md b/src/getting-started.md index da444cdb..8b2fc48f 100644 --- a/src/getting-started.md +++ b/src/getting-started.md @@ -181,7 +181,7 @@ should still read the rest of the section: | Command | When to use it | | --- | --- | -| `x.py check` | Quick check to see if things compile; rust-analyzer can run this automatically for you | +| `x.py check` | Quick check to see if things compile; [rust-analyzer can run this automatically for you][rust-analyzer] | | `x.py build --stage 0 [library/std]` | Build only the standard library, without building the compiler | | `x.py build library/std` | Build just the 1st stage of the compiler, along with the standard library; this is faster than building stage 2 and usually good enough | | `x.py build --keep-stage 1 library/std` | Build the 1st stage of the compiler and skips rebuilding the standard library; this is useful after you've done an ordinary stage1 build to skip compilation time, but it can cause weird problems. (Just do a regular build to resolve.) | @@ -230,6 +230,7 @@ test are mostly for the frontend of the compiler, so if you are working on LLVM or codegen, this shortcut will _not_ test your changes. You can read more about the different test suites [in this chapter][testing]. +[rust-analyzer]: ./building/suggested.html#configuring-rust-analyzer-for-rustc [uitests]: ./tests/adding.html#ui [testing]: https://rustc-dev-guide.rust-lang.org/tests/intro.html