aboutsummaryrefslogtreecommitdiff
path: root/crates/rust-analyzer/src/cli.rs
diff options
context:
space:
mode:
authorAleksey Kladov <[email protected]>2021-03-30 09:59:00 +0100
committerAleksey Kladov <[email protected]>2021-03-30 10:47:23 +0100
commit797185e1b66fb0d6ec1dedf206616890b5e3fef3 (patch)
tree8455d51018e4c395ac33d6df4174c94dbd6dbcb1 /crates/rust-analyzer/src/cli.rs
parent904bdff2241a54c6aebe0f6fd39e6560550a66b0 (diff)
internal: switch from CLI to internal benchmarking
We have a CLI for benchmarking, but no one actually uses it it seems. Let's try switching to "internal" benchmarks, implemented as rust tests. They should be easier to "script" to automate tracking of perf regressions.
Diffstat (limited to 'crates/rust-analyzer/src/cli.rs')
-rw-r--r--crates/rust-analyzer/src/cli.rs4
1 files changed, 1 insertions, 3 deletions
diff --git a/crates/rust-analyzer/src/cli.rs b/crates/rust-analyzer/src/cli.rs
index ed732eb38..76b666dc2 100644
--- a/crates/rust-analyzer/src/cli.rs
+++ b/crates/rust-analyzer/src/cli.rs
@@ -1,8 +1,7 @@
1//! Various batch processing tasks, intended primarily for debugging. 1//! Various batch processing tasks, intended primarily for debugging.
2 2
3mod load_cargo; 3pub(crate) mod load_cargo;
4mod analysis_stats; 4mod analysis_stats;
5mod analysis_bench;
6mod diagnostics; 5mod diagnostics;
7mod progress_report; 6mod progress_report;
8mod ssr; 7mod ssr;
@@ -15,7 +14,6 @@ use syntax::{AstNode, SourceFile};
15use vfs::Vfs; 14use vfs::Vfs;
16 15
17pub use self::{ 16pub use self::{
18 analysis_bench::{BenchCmd, BenchWhat, Position},
19 analysis_stats::AnalysisStatsCmd, 17 analysis_stats::AnalysisStatsCmd,
20 diagnostics::diagnostics, 18 diagnostics::diagnostics,
21 load_cargo::{load_workspace, load_workspace_at, LoadCargoConfig}, 19 load_cargo::{load_workspace, load_workspace_at, LoadCargoConfig},