rust/tests at 874a5f80c74851aa142a196be49b73f55bd1c619 - rust

History

Aleksey Kladov 874a5f80c7 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.	2020-06-25 08:01:03 +02:00
..
heavy_tests	Scale progress down	2020-06-25 08:01:03 +02:00

Aleksey Kladov 874a5f80c7 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.

2020-06-25 08:01:03 +02:00

heavy_tests

Scale progress down

2020-06-25 08:01:03 +02:00