7 releases (breaking)

Uses old Rust 2015

0.8.1-rc1 May 24, 2021
0.8.0 May 24, 2021
0.7.0 Jun 12, 2020
0.6.0 Jan 2, 2020
0.3.0 Jun 14, 2016

#849 in Rust patterns

Download history 33/week @ 2023-11-26 30/week @ 2023-12-03 4/week @ 2023-12-10 22/week @ 2023-12-17 16/week @ 2023-12-24 9/week @ 2023-12-31 24/week @ 2024-01-07 22/week @ 2024-01-14 11/week @ 2024-01-21 1/week @ 2024-01-28 6/week @ 2024-02-04 14/week @ 2024-02-11 25/week @ 2024-02-18 65/week @ 2024-02-25 29/week @ 2024-03-03 14/week @ 2024-03-10

135 downloads per month
Used in 4 crates (via osmio)

AGPL-3.0

30KB
433 lines

iter-progress

Build Status Crates.io Documentation

Wrap an iterator, and get progress data as it's executed. A more advanced .enumerate()

Documentation

Wrap an iterator, and get progress data as it's executed. A more advanced .enumerate()

Usage

Call .progress() on any Iterator, and get a new iterator that yields (ProgressRecord, T), where T is the original value. A ProgressRecord has many helpful methods to query the current state of the iterator

At every iteration, the current time is calculated. For iterators generating lots of items per second, this might be a noticable performance hit. Use .optional_progress(N) to generate a new iterator that yields (Option<ProgressRecord>, T). Every N items, the result will be (Some(ProgressRecord), T), otherwise (None, T) is returned and no call to get the current time is made.

Example

use iter_progress::ProgressableIter;
// Create an iterator that goes from 0 to 1,000
let my_iter = 0..1_000;
let mut progressor = my_iter.progress();

// This new iterator returns a struct with the current state, and the inner object returned by
// the iterator
let (state, number) = progressor.next().unwrap();
assert_eq!(number, 0);

// We can now use methods on `state` to find out about this object

// If we know the size of the iterator, we can query how far we are through it
// How far through the iterator are we. 0 to 1
assert_eq!(state.fraction(), Some(0.001));

// We are 0.1% the way through
assert_eq!(state.percent(), Some(0.1));

Another usage:

use iter_progress::ProgressableIter;
let my_big_vec = vec![false; 100];

for (state, val) in my_big_vec.iter().progress() {
    // Every 1 second, execute this function with the the `state`
    state.do_every_n_sec(1., |state| {
       println!("{}% the way though, and doing {} per sec.", state.percent().unwrap(), state.rate());
    });

    // Do something to process `val`
}

.do_every_n_sec is a "best effort" attempt. It's single threaded, so will be called if the last time that was called was more than N sec ago. .do_every_n_items is called every N items.

No runtime deps