Releases: GitoxideLabs/prodash
v26.1.0
New Features
- add
progress::AtomicStep
to allow referring to it.
Previously, onlyStepShared
was available, which implies anArc
.
Commit Statistics
- 1 commit contributed to the release.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Add
progress::AtomicStep
to allow referring to it. (0705a73)
- Add
v26.0.0
This release is all about making dyn
possible both for nested progress, as well as for 'simple' one (previously known as RawProgress
).
Switching to this release naturally makes it possible for users of Progress
to also use dyn Progress
, as this trait is now object safe (formerly RawProgress
).
If there are compile errors, the code now needs NestedProgress
, instead of Progress
, and possibly the import of the Count
trait.
Finally, it's recommended to review all usages of Progress
as they can possibly be replaced with Count
which provides the guarantee that only counting happens,
and no change of the progress information itself.
New Features (BREAKING)
- split
Progress
into various super-traits to allow most of them to be dyn-safe.
Progress
is nowNestedProgress
,RawProgress
is nowProgress
, and there is
a newCount
trait for solely counting things. Progress::counter()
is now mandatory.
This should simplify downstream code and we just accept that we are dealing
with a threaded world.
This also comes with performance improvements as increments are now 250% faster.
Commit Statistics
- 8 commits contributed to the release.
- 13 days passed between releases.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Merge branch 'simplify' (5e21df7)
Progress::counter()
is now mandatory. (6c60835)- Prepare release (e1e282a)
- Fixup nested dyn-traits (5e76abf)
- Merge branch 'feat/dyn-progress' into simplify (c1590e4)
- Split
Progress
into various super-traits to allow most of them to be dyn-safe. (6aba6e3) - Add benchmarks for dyn-traits (9d03124)
- Refactor (54094b6)
v25.0.2
Chore
- Adjusting changelogs prior to release of prodash v25.0.2
Commit Statistics
- 2 commits contributed to the release.
- 37 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v25.0.1
Bug Fixes
log
progress now supports a shared counter, just like the tree-item implementation
Commit Statistics
- 3 commits contributed to the release.
- 60 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v25.0.0
New Features
-
Introduce the object-safe
RawProgress
trait.
It's automatically implemented forProgress
and allows for more flexible use
of progress particularly in leaf nodes. This is useful if a function needs to take
multiple types of progress as it is called from different places in the same function.Without dyn-traits, it's not possible to make such call.
New Features (BREAKING)
- Make messaging functions thread-safe by taking shared borrow and requring
Sync
.
That way it's possible to share theRawProgress
object across threads and emit messages,
much like a logging system that's more integrated with rendering.
Commit Statistics
- 2 commits contributed to the release.
- 5 days passed between releases.
- 2 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v24.0.0
Chore (BREAKING)
- switch from
tui
toratatui
.
The latter is a maintained fork.
Commit Statistics
- 3 commits contributed to the release.
- 60 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Thanks Clippy
Clippy helped 1 time to make code idiomatic.
Commit Details
v23.1.2
Bug Fixes
-
line renderer now properly detects changes.
Previously change-detection was implemented based on the assumption that
the progress tree is copied entirely. Now, however, the interesting values
are shared.The change-detection was adjusted to keep the state's hash of the most recent
drawing, instead of doing everything in line, which saves time hashing as well.
Commit Statistics
- 1 commit contributed to the release.
- 9 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Line renderer now properly detects changes. (7966f79)
v23.1.1
A maintenance release without user-facing changes.
Most notably, parking_lot
was upgraded to the latest version.
Commit Statistics
- 2 commits contributed to the release.
- 2 days passed between releases.
- 0 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v23.1.0
New Features
-
improve performance of
progress::tree
operations by more than 50%.
This was done by implementing shared state in a simple Mutex protected hashmap
which for typical programs with less contention is faster than using thedashmap
crate.However, for those who know they need it, the previous implementation is still available
in with theprogress-tree-hp-hashmap
feature toggle.
Commit Statistics
- 3 commits contributed to the release.
- 61 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
v23.0.0
New Features (BREAKING)
- Implement
Hash
forTask
to avoid redrawing if nothing changes with the Line renderer.
That way, if everything stops due to a user prompt, the user's input won't be clobbered
continnuously.
Commit Statistics
- 1 commit contributed to the release.
- 23 days passed between releases.
- 1 commit was understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- Implement
Hash
forTask
to avoid redrawing if nothing changes with the Line renderer. (a1db1b2)
- Implement