6317292cd5
It doesn't make sense for the prime_caches itself send begin/end events -- the caller knows perfectly fine when they happen!
35 lines
1.3 KiB
Rust
35 lines
1.3 KiB
Rust
//! rust-analyzer is lazy and doesn't compute anything unless asked. This
|
|
//! sometimes is counter productive when, for example, the first goto definition
|
|
//! request takes longer to compute. This modules implemented prepopulation of
|
|
//! various caches, it's not really advanced at the moment.
|
|
|
|
use hir::db::DefDatabase;
|
|
use ide_db::base_db::SourceDatabase;
|
|
|
|
use crate::RootDatabase;
|
|
|
|
/// We started indexing a crate.
|
|
#[derive(Debug)]
|
|
pub struct PrimeCachesProgress {
|
|
pub on_crate: String,
|
|
pub n_done: usize,
|
|
pub n_total: usize,
|
|
}
|
|
|
|
pub(crate) fn prime_caches(db: &RootDatabase, cb: &(dyn Fn(PrimeCachesProgress) + Sync)) {
|
|
let _p = profile::span("prime_caches");
|
|
let graph = db.crate_graph();
|
|
let topo = &graph.crates_in_topological_order();
|
|
|
|
// FIXME: This would be easy to parallelize, since it's in the ideal ordering for that.
|
|
// Unfortunately rayon prevents panics from propagation out of a `scope`, which breaks
|
|
// cancellation, so we cannot use rayon.
|
|
for (i, &crate_id) in topo.iter().enumerate() {
|
|
let crate_name = graph[crate_id].display_name.as_deref().unwrap_or_default().to_string();
|
|
|
|
cb(PrimeCachesProgress { on_crate: crate_name, n_done: i, n_total: topo.len() });
|
|
db.crate_def_map(crate_id);
|
|
db.import_map(crate_id);
|
|
}
|
|
}
|