Skip to main content

Module progress

Module progress 

Source
Expand description

Progress-reporting port for registry fetch tasks.

ProgressSender lets a fetch task report fetched/total progress without knowing whether, or how, anything renders it — a driving adapter drains the paired mpsc::Receiver<ProgressUpdate> returned by channel however it sees fit (deps-lsp’s RegistryProgress drives the LSP work-done-progress protocol from it; deps-cli may render a terminal progress bar the same way, or drop the receiver and pass None as the sender).

Structs§

ProgressSender
Non-blocking sender for progress updates from fetch tasks.
ProgressUpdate
A single fetch-progress observation: fetched out of total packages processed so far.

Functions§

channel
Creates a progress port: a ProgressSender fetch tasks report through, paired with the Receiver a driving adapter drains to render progress however it sees fit.