lib-wc
A simple rust library (by wcygan)
zentime-rs
Pomodoro + Productivity timer written in Rust (by on3iro)
| lib-wc | zentime-rs | |
|---|---|---|
| 1 | 5 | |
| 4 | 12 | |
| - | - | |
| 3.0 | 4.1 | |
| about 1 year ago | 10 months ago | |
| Rust | Rust | |
| - | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lib-wc
Posts with mentions or reviews of lib-wc.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-09.
zentime-rs
Posts with mentions or reviews of zentime-rs.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-09.
-
Better pattern instead of callback closures?
I am in the midst of refactoring a library I wrote, but am a bit stuck. The library is for pomodoro-timers. Up to this point I used a single type state pattern to describe a paused and a running timer. All other state like breaks etc. where carried in a shared state property. The timer is synchronous and currently should always be run inside another thread/task and interacts with the calling code via two callbacks on_tick and on_timer_end. The on_tick callback closure returns a Option that way the timer can react to external input on each tick. Here's the old timer: https://github.com/on3iro/zentime-rs/blob/main/timer/src/timer.rs
- Having trouble creating a server client in Rust
-
Is there a way to send a system notification from a daemon written in Rust?
So maybe I am still having some kind of fundamental misunderstanding, why my code is "bad" (although it seems to work correctly now) or you might have looked at some older code? Hm. This is my latest revision: https://github.com/on3iro/zentime-rs/releases/tag/0.5.2
-
Trouble wrapping my head around async
If you would like to see the code in question, here is a link to the branch with the async part and the specific entry point: https://github.com/on3iro/zentime-rs/blob/async-capabilities/src/default_cmd.rs
What are some alternatives?
When comparing lib-wc and zentime-rs you can also consider the following projects:
seize - Fast, efficient, and robust memory reclamation for Rust.
gryf - Graph data structure library aspiring to be convenient, versatile, correct and performant.
r3bl-open-core - TUI framework and developer productivity apps in Rust 🦀
leapfrog - Lock-free concurrent and single-threaded hash map implementations using Leapfrog probing. Currently the highest performance concurrent HashMap in Rust for certain use cases.
Rust - All Algorithms implemented in Rust
crossbeam - Tools for concurrent programming in Rust
rust-algorithms - Common data structures and algorithms in Rust