seize
Fast, efficient, and robust memory reclamation for Rust. (by ibraheemdev)
cactusref
🌵 Cycle-Aware Reference Counting in Rust (by artichoke)
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.
seize
Posts with mentions or reviews of seize.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-05-03.
- Seize - Fast, efficient, and robust memory reclamation for Rust.
-
As part of the stdlib mutex overhaul, std::sync::Mutex on Linux now has competitive performance with parking_lot
Recently I learned about the hyaline reclamation scheme that seize uses. Mentioning since it may interest you:flurry, a concurrent HashMap, recently switched from crossbeam-epoch (based on epoch GC) to seize.
- Seize – Fast, efficient, and robust memory reclamation for Rust
- Seize: Fast, efficient, and robust memory reclamation
- Seize: Fast, efficient, and robust memory reclamation for concurrent data structures.
cactusref
Posts with mentions or reviews of cactusref.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-08-12.
-
Why Can't `Box` Be Abstracted Away From the Developer?
Absolutely. I have seen some pretty cool concepts in Rust for memory cleanup; not just garbage collection, but deterministic reference cycle removal by cactusref. And the fun thing about these is that you still get all of Rust's zero-cost abstractions and epic modern language design.
-
CactusRef: an experimental cycle-aware Rc and mini tracing GC
I've put together a WIP PR to experiment with a safe adoption API: https://github.com/artichoke/cactusref/pull/47. This allows the doubly linked list example to be implemented in safe code without leaks. I didn't even think this was possible! Thanks for making me think!
What are some alternatives?
When comparing seize and cactusref you can also consider the following projects:
mmtk-core - Memory Management ToolKit
book - Writing Interpreters in Rust: a Guide
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...
librseq - Library for Restartable Sequences
rust-wiki-backup - A backup of the Rust wiki
flurry - A port of Java's ConcurrentHashMap to Rust
AGC - Garbage collection for Ada
lib-wc - A simple rust library
artichoke - 💎 Artichoke is a Ruby made with Rust
yew - Rust / Wasm framework for creating reliable and efficient web applications
luau - A fast, small, safe, gradually typed embeddable scripting language derived from Lua