static-rc
wg-allocators
static-rc | wg-allocators | |
---|---|---|
4 | 18 | |
418 | 199 | |
- | 5.5% | |
0.0 | 0.0 | |
12 months ago | about 3 years ago | |
Rust | ||
Apache License 2.0 | - |
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.
static-rc
- StaticRc: Compile-Time Reference Counting
-
Which important features from C/C++ are missing in Rust
It can... it's not too ergonomic though because you need to manually specify the size of the return array as it cannot be the result of an expression. (See static-rc for an example of usage)
-
Data Modelling in Rust Continued
You can also combine GhostCell with StaticRc (compile time rc) and avoid runtime overhead.
-
Is it possible to write overhead-free cyclic data-structures in safe, stable Rust?
I submitted a pull request for this.
wg-allocators
-
Anouncing `stabby` 1.0!
Tracking issue for Storages, and a TLDR on what it is
- What backwards-incompatible changes would you make in a hypothetical Rust 2.0?
-
Custom allocators in Rust
I must have gotten confused, since from your brief discussion with CAD97 it seemed like there was a way for the concepts to live separately and that Storage could complicate things in comparison. But if implementing Allocator in terms of Storage is basically equivalent and Storage is flexible enough that I could write one to pass memory out to unsafe code, that works just as well.
-
Zig and Rust
https://rust-lang.github.io/rfcs/1974-global-allocators.html was the original RFC.
My vague understanding is that there's a working group https://github.com/rust-lang/wg-allocators
The further I get from working on Rust day to day, the less I know about these things, so that's all I've got for you.
-
Rust went from side project to world’s fastest growing language
If you self-reference using pointers and guarantee the struct will never move, you don't even need unsafe. If you self-reference using offsets from the struct's base pointer, you need a splash of unsafe but your struct can be freely moved without invalidating its self-referential "pointers".
Per-struct allocators are a work in progress (see https://github.com/rust-lang/wg-allocators/issues/48).
Not sure what "non thread local addresses" means, but in my experience Rust is pretty good at sending data between threads (without moving it).
- Rust is coming to the Linux kernel
-
FunDSP 0.1.0, an audio processing and synthesis library
Besides that allocation is not really a problem for no_std. It's resolved by using alloc crate directly, so anything usable with custom allocators is supported. Example in dasp sources - https://github.com/RustAudio/dasp/blob/master/dasp_slice/src/boxed.rs#L14-L19 . Also worth looking at this issue to check what is usable already - https://github.com/rust-lang/wg-allocators/issues/7
-
Andrew Kelley claims Zig is faster than Rust in perfomance
But that's on track for rust as well: https://github.com/rust-lang/wg-allocators/issues/7
-
Which important features from C/C++ are missing in Rust
Here: https://github.com/rust-lang/rfcs/pull/1398. there is also a working group for this: https://github.com/rust-lang/wg-allocators.
-
Box<T> allocator override?
It's unstable. wg-allocators contains discussions about design and a tracking issue for collections that need an allocator https://github.com/rust-lang/wg-allocators/issues/7
What are some alternatives?
ghost-collections - Safe collections written in stable Rust, based on GhostCell and StaticRc.
www.ziglang.org
rust - Empowering everyone to build reliable and efficient software.
serde-plain - A serde serializer that serializes a subset of types into plain strings
rfcs - RFCs for changes to Rust
enum-map
bevy - A refreshingly simple data-driven game engine built in Rust
rules_rust - Rust rules for Bazel
cryptography - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.
dpp - Directly include C headers in D source code
fuzzcheck-rs - Modular, structure-aware, and feedback-driven fuzzing engine for Rust functions
redbpf - Rust library for building and running BPF/eBPF modules