this post was submitted on 25 Apr 2024
42 points (100.0% liked)
Rust
5651 readers
12 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Huh, this is awesome! From the link, this now works:
I'm going to have to play with this to see how far it goes.
Wouldn't this just prevent you from allocating more memory (than zero)?
Ah, apparently for now you're not allowed to allocate. But
vec::new_in(allocator)
looks interesting. This works in nightly today:Maybe at some point I can append to it at compile time too. I'd love to be able to put a
const {}
and have allocations that resolve down to a'static
, and this seems to be a step toward that.I guess I'm just excited that
Vec::new()
is the example they picked, since the next obvious question is, "can I push?"What I'm curious about - this function was already const, so for stuff like this, I'd think there's basically a 100% chance the compiler would optimize this too, just implicitly.
AFAIK this new feature is just for times when it isn't an optimization, but more your own domain invariants. E.g. assertions.
But I could be wrong. I wonder if this can be used for actual optimizations in some places that the compiler couldn't figure out by itself.