u/Luroalivein r/rust • Recommends
On “Enabling `if` and `match` in constants on nightly”
Maybe this article helps you
https://varkor.github.io/blog/2019/01/11/const-types-traits-and-implementations-in-Rust.html
link to this video
0:00 / 0:00
RustConf 2019 - Taking Constant Evaluation to the Limit by Oliver Schneider
Rust Programming Language
70K subscribers • 72 videos on Hallway • Conference channel
- Recommended by 2 people: 2 in engineering communities.
- Presented by Oliver Schneider
Advanced. Deep dive for people who know the field.
7.6K views7 years ago2 recommendations
Programming languagesSystems programmingRustCompilers and interpretersPerformance and optimization
Oliver Schneider explains the inner workings of Miri, the compile-time constant evaluator in the Rust compiler.
RustConf 2019 - Taking Constant Evaluation to the Limit by Oliver Schneider Have you ever wanted to write a static with a complex initial value? Are you programming microcontrollers? Do you want to run as little code as possible at runtime or are you trying to reduce your memory footprint? If you answered yes to any of these questions, then you probably want to evaluate all-the-things™ at compile-time with a constant evaluator. This talk will focus on explaining the inner workings of the new theoretically unrestricted constant evaluator in rustc (nicknamed Miri for "MIR interpreter") and give a short outlook on the future features Miri will enable in the Rust language.Why it's here
2 people recommend thisWhat people say. Recommended for understanding how Rust evaluates code at compile time and the future of const evaluation.
Moments people linked to
u/matkladrust-analyzerin r/rust • Recommends
On “Rust’s Intentions Towards Compile Time Programming”
I believe that is possible and plannd: link to this video
The idea is that we'll introduce a `ConstSafe` auto-trait, like `Sync`, which promises that the type won't touch "heap" memory. So, something like `&Box<AtomicUsize>` would not be const-safe, but `&Box<usize>` would.