mirror of
https://github.com/rust-lang/rust.git
synced 2025-01-30 16:43:41 +00:00
874a5f80c7
There are two reasons why we don't want a generic ra_progress crate just yet: *First*, it introduces a common interface between separate components, and that is usually undesirable (b/c components start to fit the interface, rather than doing what makes most sense for each particular component). *Second*, it introduces a separate async channel for progress, which makes it harder to correlate progress reports with the work done. Ie, when we see 100% progress, it's not blindly obvious that the work has actually finished, we might have some pending messages still. |
||
---|---|---|
.. | ||
paths | ||
ra_arena | ||
ra_assists | ||
ra_cfg | ||
ra_db | ||
ra_flycheck | ||
ra_fmt | ||
ra_hir | ||
ra_hir_def | ||
ra_hir_expand | ||
ra_hir_ty | ||
ra_ide | ||
ra_ide_db | ||
ra_mbe | ||
ra_parser | ||
ra_proc_macro | ||
ra_proc_macro_srv | ||
ra_prof | ||
ra_project_model | ||
ra_ssr | ||
ra_syntax | ||
ra_text_edit | ||
ra_toolchain | ||
ra_tt | ||
rust-analyzer | ||
stdx | ||
test_utils | ||
vfs | ||
vfs-notify |