diff options
Diffstat (limited to 'docs')
-rw-r--r-- | docs/dev/README.md | 8 | ||||
-rw-r--r-- | docs/dev/architecture.md | 4 |
2 files changed, 4 insertions, 8 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md index c834a3ff8..ba24524f2 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md | |||
@@ -113,7 +113,7 @@ communication, and `print!` would break it. | |||
113 | If I need to fix something simultaneously in the server and in the client, I | 113 | If I need to fix something simultaneously in the server and in the client, I |
114 | feel even more sad. I don't have a specific workflow for this case. | 114 | feel even more sad. I don't have a specific workflow for this case. |
115 | 115 | ||
116 | Additionally, I use `cargo run --release -p ra_cli -- analysis-stats | 116 | Additionally, I use `cargo run --release -p ra_lsp_server -- analysis-stats |
117 | path/to/some/rust/crate` to run a batch analysis. This is primarily useful for | 117 | path/to/some/rust/crate` to run a batch analysis. This is primarily useful for |
118 | performance optimizations, or for bug minimization. | 118 | performance optimizations, or for bug minimization. |
119 | 119 | ||
@@ -170,12 +170,12 @@ In particular, I have `export RA_PROFILE='*>10'` in my shell profile. | |||
170 | To measure time for from-scratch analysis, use something like this: | 170 | To measure time for from-scratch analysis, use something like this: |
171 | 171 | ||
172 | ``` | 172 | ``` |
173 | $ cargo run --release -p ra_cli -- analysis-stats ../chalk/ | 173 | $ cargo run --release -p ra_lsp_server -- analysis-stats ../chalk/ |
174 | ``` | 174 | ``` |
175 | 175 | ||
176 | For measuring time of incremental analysis, use either of these: | 176 | For measuring time of incremental analysis, use either of these: |
177 | 177 | ||
178 | ``` | 178 | ``` |
179 | $ cargo run --release -p ra_cli -- analysis-bench ../chalk/ --highlight ../chalk/chalk-engine/src/logic.rs | 179 | $ cargo run --release -p ra_lsp_server -- analysis-bench ../chalk/ --highlight ../chalk/chalk-engine/src/logic.rs |
180 | $ cargo run --release -p ra_cli -- analysis-bench ../chalk/ --complete ../chalk/chalk-engine/src/logic.rs:94:0 | 180 | $ cargo run --release -p ra_lsp_server -- analysis-bench ../chalk/ --complete ../chalk/chalk-engine/src/logic.rs:94:0 |
181 | ``` | 181 | ``` |
diff --git a/docs/dev/architecture.md b/docs/dev/architecture.md index 9675ed0b6..41c3909f7 100644 --- a/docs/dev/architecture.md +++ b/docs/dev/architecture.md | |||
@@ -147,10 +147,6 @@ different from data on disk. This is more or less the single really | |||
147 | platform-dependent component, so it lives in a separate repository and has an | 147 | platform-dependent component, so it lives in a separate repository and has an |
148 | extensive cross-platform CI testing. | 148 | extensive cross-platform CI testing. |
149 | 149 | ||
150 | ### `crates/ra_cli` | ||
151 | |||
152 | A CLI interface to rust-analyzer, mainly for testing. | ||
153 | |||
154 | ## Testing Infrastructure | 150 | ## Testing Infrastructure |
155 | 151 | ||
156 | Rust Analyzer has three interesting [systems | 152 | Rust Analyzer has three interesting [systems |