rust-djangohashers VS wg-allocators

Compare rust-djangohashers vs wg-allocators and see what are their differences.

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)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
rust-djangohashers wg-allocators
1 18
55 188
- 0.0%
5.4 0.0
about 2 months ago about 3 years ago
Rust
GNU General Public License v3.0 or later -
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.

rust-djangohashers

Posts with mentions or reviews of rust-djangohashers. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-07.

wg-allocators

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

What are some alternatives?

When comparing rust-djangohashers and wg-allocators you can also consider the following projects:

orion - Usable, easy and safe pure-Rust crypto [Moved to: https://github.com/orion-rs/orion]

www.ziglang.org

rust-security-framework - Bindings to the macOS Security.framework

serde-plain - A serde serializer that serializes a subset of types into plain strings

ed25519-dalek - Fast and efficient ed25519 signing and verification in Rust.

enum-map

schannel-rs - Schannel API-bindings for rust (provides an interface for native SSL/TLS using windows APIs)

rules_rust - Rust rules for Bazel

octavo - Highly modular & configurable hash & crypto library

cryptography - cryptography is a package designed to expose cryptographic primitives and recipes to Python developers.

webpki - WebPKI X.509 Certificate Validation in Rust

dpp - Directly include C headers in D source code