wg-allocators

Home of the Allocators working group: Paving a path for a standard set of allocator traits to be used in collections! (by rust-lang)

Wg-allocators Alternatives

Similar projects and alternatives to wg-allocators

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better wg-allocators alternative or higher similarity.

wg-allocators reviews and mentions

Posts with mentions or reviews of wg-allocators. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-03.
  • Anouncing `stabby` 1.0!
    6 projects | /r/rust | 3 Jun 2023
    Tracking issue for Storages, and a TLDR on what it is
  • What backwards-incompatible changes would you make in a hypothetical Rust 2.0?
    10 projects | /r/rust | 19 Apr 2023
  • Custom allocators in Rust
    4 projects | /r/rust | 6 Apr 2023
    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
    6 projects | news.ycombinator.com | 27 Mar 2023
    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
    7 projects | news.ycombinator.com | 14 Feb 2023
    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
    7 projects | /r/programming | 20 Sep 2022
  • FunDSP 0.1.0, an audio processing and synthesis library
    3 projects | /r/rust | 31 Jan 2022
    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
    1 project | /r/rust | 16 Jan 2022
    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
    9 projects | /r/rust | 18 Dec 2021
    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?
    1 project | /r/rust | 19 Aug 2021
    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
  • A note from our sponsor - InfluxDB
    www.influxdata.com | 26 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →