v17.0.0

New Features (BREAKING)

• Add MessageLevel parameter to Progress::show_throughput_with(…, level)
  This allows to use message level for highlighting of certain
  throughputs and results.

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • Add MessageLevel parameter to Progress::show_throughput_with(…, level) (46214a3)

v16.1.3

Bug Fixes

• Progress::init(None, None) now resets the progress entirely

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • Progress::init(None, None) now resets the progress entirely (2fe3eeb)

v16.1.2

Bug Fixes

• reset the shared value on init to avoid keeping the previously set value.

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • reset the shared value on init to avoid keeping the previously set value. (aa70a27)

v16.1.1

Bug Fixes

• correct signature of new 'running()' method

Commit Statistics

• 1 commit contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • correct signature of new 'running()' method (ca5f544)

v16.1.0

New Features

• Setting the progress value is now 9x faster
  This is accomplished at the cost of not autoamtically setting the
  progress to 'running' anymore when the progress is set.

Commit Statistics

• 2 commits contributed to the release.
• 1 commit where understood as conventional.
• 0 issues like '(#ID)' where seen in commit messages

Commit Details

view details

• Uncategorized
  • Setting the progress value is now 9x faster (3886754)
  • An experiment to show we don't want to rely on dashmap for this (4f527c1)

v16.0.1

Commit Statistics

• 5 commits contributed to the release over the course of 47 calendar days.
• 1 commit where understood as conventional.
• 1 unique issue was worked on: #8

Thanks Clippy

Clippy helped 1 time to make code idiomatic.

Commit Details

view details

• #8
  • Run cargo changelog --write for an improved changelog (a1054e8)
• Uncategorized
  • upgrade dashmap to latest version (e6f53d5)
  • cleanup changelog (5aa6275)
  • thanks clippy (c1258e2)
  • Looks like array syntax isn't supported anymore (bfbce01)