aboutsummaryrefslogtreecommitdiff
path: root/crates/ra_syntax/test_data/parser/fuzz-failures/0004.rs
diff options
context:
space:
mode:
authorAleksey Kladov <[email protected]>2020-06-25 07:01:03 +0100
committerAleksey Kladov <[email protected]>2020-06-25 07:01:03 +0100
commit874a5f80c74851aa142a196be49b73f55bd1c619 (patch)
tree0ff97656e30c9b1fe3c4bb96b0171f33890c11ee /crates/ra_syntax/test_data/parser/fuzz-failures/0004.rs
parent76a530242a12f75e2a8456f952cef07e2d564f67 (diff)
Scale progress down
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.
Diffstat (limited to 'crates/ra_syntax/test_data/parser/fuzz-failures/0004.rs')
0 files changed, 0 insertions, 0 deletions