- Rust 100%
|
Some checks failed
CI / test (beta) (push) Failing after 3s
CI / test (nightly) (push) Failing after 4s
CI / test (nightly, i686-unknown-linux-gnu) (push) Failing after 3s
CI / test (stable) (push) Failing after 3s
CI / msrv (push) Failing after 3s
CI / clippy (push) Failing after 10s
CI / loom (push) Failing after 9s
CI / miri (push) Successful in 4m12s
CI / fmt (push) Has been cancelled
CI / security_audit (push) Has been cancelled
Two strategies are available: - FIFO: The original round-robin queuing; listeners are inserted at the back. - LIFO: The new most-recent queuing; listeners are inserted at the front. LIFO queuing is beneficial for cache-efficiency with workloads that are tolerant of starvation. The same listener is repeatedly drawn from the list until the load dictates additional listeners be drawn from the list. These listeners expand outward as a "hot set" for optimal reuse of resources rather than continuously drawing from the coldest resources in a FIFO schedule. Signed-off-by: Jason Volk <jason@zemos.net> |
||
|---|---|---|
| .github | ||
| benches | ||
| examples | ||
| src | ||
| tests | ||
| .gitignore | ||
| Cargo.toml | ||
| CHANGELOG.md | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
event-listener
Notify async tasks or threads.
This is a synchronization primitive similar to eventcounts invented by Dmitry Vyukov.
You can use this crate to turn non-blocking data structures into async or blocking data structures. See a simple mutex implementation that exposes an async and a blocking interface for acquiring locks.
Examples
Wait until another thread sets a boolean flag:
use std::sync::atomic::{AtomicBool, Ordering};
use std::sync::Arc;
use std::thread;
use std::time::Duration;
use event_listener::Event;
let flag = Arc::new(AtomicBool::new(false));
let event = Arc::new(Event::new());
// Spawn a thread that will set the flag after 1 second.
thread::spawn({
let flag = flag.clone();
let event = event.clone();
move || {
// Wait for a second.
thread::sleep(Duration::from_secs(1));
// Set the flag.
flag.store(true, Ordering::SeqCst);
// Notify all listeners that the flag has been set.
event.notify(usize::MAX);
}
});
// Wait until the flag is set.
loop {
// Check the flag.
if flag.load(Ordering::SeqCst) {
break;
}
// Start listening for events.
let listener = event.listen();
// Check the flag again after creating the listener.
if flag.load(Ordering::SeqCst) {
break;
}
// Wait for a notification and continue the loop.
listener.wait();
}
Features
-
The
stdfeature (enabled by default) enables the use of the Rust standard library. Disable it forno_stdsupport. -
The
critical-sectionfeature enables usage of thecritical-sectioncrate to enable a more efficient implementation ofevent-listenerforno_stdplatforms. -
The
portable-atomicfeature enables the use of theportable-atomiccrate to provide atomic operations on platforms that don't support them.
In production environments, at least one of std or critical-section should be
enabled. This ensures that the internal locking mechanism has a critical section of some
kind to fall back on. Otherwise, it falls back to a spinlock implementation. This
implementation is dangerous to rely on.
License
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)
at your option.
Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.