devtimer 2.0.0

A simple library that provides a simple way to time operations
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46

# Changelog
All changes in this project will be noted in this file.
## Version 2.0.0 [2020-05-09]
> No breaking changes in this release

This release adds the new `run_through()` feature. This new feature completes the gap that was left
in building the _complete_ benchmarking suite for Rust. A single benchmark doesn't say much, so
it is far better to run the benchmark over and over again to see how it perform on average.
The `run_through()` function does exactly that. It accepts the number of iterations as an `usize`
and the benchmark code, either as a closure (`|| {}`) or a function directly. So now that you've
got a complete benchmarking suite, why not benchmark some code?

## Version 1.1.2 [2019-11-27]
> No breaking changes in this release

Fixed minor issues with the documentation which were slightly misleading
## Version 1.1.1 [2019-11-17]
> This release introduces breaking changes!

Take a reference to `std::time::duration` instead of taking it's ownership.
#### Upgrading exisiting code
If you had done something like `timer.start_after(std::time::Duration::from_secs(2))`, all you need to do is add a borrow like shown below:
```rust
timer.start_after(&std::time::Duration::from_secs(2))
```
#### Reason for change
If a common variable is used by the developer, i.e it is declared as follows:
```rust
let dur = std::time::Duration::from_secs(2);
```
Then giving ownership to `start_after()` will be a problem. That is why, this design change was made. Hence, from now on, all you do is:
```rust
let mut timer = DevTime::new();
timer.start_after(&dur);
```

## Version 1.1.0 [2019-11-16]
> No breaking changes in this release
- This version introduces a new function `start_after()`. This can be used to delay the starting of timer operations

## Version 1.0.1 [2019-11-11]
> No breaking changes in this release
- This fixed some issues with the documentation

## Version 1.0.0 [2019-11-10]
- This is the initial release of the crate