@@ -19,10 +19,10 @@ All contributors are expected to follow the [Rust Code of Conduct].
1919 - [ Writing code] ( #writing-code )
2020 - [ Getting code-completion for rustc internals to work] ( #getting-code-completion-for-rustc-internals-to-work )
2121 - [ How Clippy works] ( #how-clippy-works )
22- - [ Fixing build failures caused by Rust ] ( #fixing-build-failures-caused-by -rust)
22+ - [ Syncing changes between Clippy and [ ` rust-lang/rust ` ]] ( #syncing-changes-between-clippy-and -rust-langrust )
2323 - [ Patching git-subtree to work with big repos] ( #patching-git-subtree-to-work-with-big-repos )
24- - [ Performing the sync] ( #performing-the-sync )
25- - [ Syncing back changes in Clippy to [ ` rust-lang/rust ` ]] ( #syncing-back-changes-in -clippy-to-rust-langrust )
24+ - [ Performing the sync from [ ` rust-lang/rust ` ] to Clippy ] ( #performing-the-sync-from-rust-langrust-to-clippy )
25+ - [ Performing the sync from Clippy to [ ` rust-lang/rust ` ]] ( #performing-the-sync-from -clippy-to-rust-langrust )
2626 - [ Defining remotes] ( #defining-remotes )
2727 - [ Issue and PR triage] ( #issue-and-pr-triage )
2828 - [ Bors and Homu] ( #bors-and-homu )
@@ -111,7 +111,7 @@ To work around this, you need to have a copy of the [rustc-repo][rustc_repo] ava
111111` git clone https://github.com/rust-lang/rust/ ` .
112112Then you can run a ` cargo dev ` command to automatically make Clippy use the rustc-repo via path-dependencies
113113which rust-analyzer will be able to understand.
114- Run ` cargo dev ra-setup --repo-path <repo-path> ` where ` <repo-path> ` is an absolute path to the rustc repo
114+ Run ` cargo dev ra_setup --repo-path <repo-path> ` where ` <repo-path> ` is an absolute path to the rustc repo
115115you just cloned.
116116The command will add path-dependencies pointing towards rustc-crates inside the rustc repo to
117117Clippys ` Cargo.toml ` s and should allow rust-analyzer to understand most of the types that Clippy uses.
0 commit comments