4 ms·
This doesn't require an edition change, but I'm really looking forward to custom, per-collection allocator support. It's in nightly right now and very nice to u
by nynx 5y ago
This doesn't require an edition change, but I'm really looking forward to custom, per-collection allocator support. It's in nightly right now and very nice to use.
- swsieber 5y agoThere's been a lot of attention given to the api since the roll-out: https://internals.rust-lang.org/t/is-custom-allocators-the-right-abstraction/13460/88 https://internals.rust-lang.org/t/is-custom-allocators-the-r... I'm not sure if the changes discussed there are going to be rolled in or not. It's certainly an interesting thread.
- nynx 5y agoYeah, I’ve been following that thread. The storage idea is interesting but I don’t think it’s really necessary. The main thing it would enable is inline allocators that can be stored inside the collection, as opposed to the collection storing a reference to the stack allocation. The cases where that’s necessary, one can use the stackvec or arrayvec crates, which are more optimized than a generic inline allocator would be anyhow.