diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2020-11-02 17:12:08 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2020-11-02 17:12:08 +0000 |
| commit | eb4e84ff510b9e5ead529dba83fc1679a569c448 (patch) | |
| tree | f39809991b96a63e43c8bab5b8a0a0479e97293c /crates/syntax/test_data/reparse/fuzz-failures | |
| parent | 4e80002aceadcff666f800d8bea7bd6e3d977946 (diff) | |
| parent | a968cb6aef24179e0c0a7f3d261fbec14e2c00d7 (diff) | |
Merge #6441
6441: Coalesce prime_caches updates r=matklad a=jonas-schievink
This reduces the number of progress bar updates we send to the client by collapsing subsequent updates into one. This doesn't work as well as I'd hoped (which is that we end up sending *no* updates, or only `start` and `end`, when the cache is already fresh), but it does reduce the number considerably: instead of ~720 updates on the rust-analyzer codebase, we now only send ~60.
It uses the same approach that is already in use for coalescing VFS events.
Hopefully this is enough to fix https://github.com/rust-analyzer/rust-analyzer/issues/6413.
Co-authored-by: Jonas Schievink <[email protected]>
Diffstat (limited to 'crates/syntax/test_data/reparse/fuzz-failures')
0 files changed, 0 insertions, 0 deletions