#math #unroll #load

no-std crunchy

Crunchy unroller: deterministically unroll constant loops

9 releases

Uses old Rust 2015

0.2.2 May 7, 2019
0.2.1 Mar 19, 2018
0.1.6 Aug 18, 2017
0.1.4 Jul 22, 2017

#72 in Development tools

Download history 507686/week @ 2023-10-18 526483/week @ 2023-10-25 534689/week @ 2023-11-01 538405/week @ 2023-11-08 535950/week @ 2023-11-15 421804/week @ 2023-11-22 448987/week @ 2023-11-29 457874/week @ 2023-12-06 489621/week @ 2023-12-13 326414/week @ 2023-12-20 273779/week @ 2023-12-27 477825/week @ 2024-01-03 486723/week @ 2024-01-10 485408/week @ 2024-01-17 489007/week @ 2024-01-24 435199/week @ 2024-01-31

1,993,896 downloads per month
Used in 8,587 crates (53 directly)

MIT license

11KB
241 lines

Crunchy

The crunchy unroller - deterministically unroll constant loops. For number "crunching".

The Rust optimizer will unroll constant loops that don't use the loop variable, like this:

for _ in 0..100 {
  println!("Hello!");
}

However, using the loop variable will cause it to never unroll the loop. This is unfortunate because it means that you can't constant-fold the loop variable, and if you end up stomping on the registers it will have to do a load for each iteration. This crate ensures that your code is unrolled and const-folded. It only works on literals, unfortunately, but there's a work-around:

debug_assert_eq!(MY_CONSTANT, 100);
unroll! {
  for i in 0..100 {
    println!("Iteration {}", i);
  }
}

This means that your tests will catch if you redefine the constant.

To default maximum number of loops to unroll is 64, but that can be easily increased using the cargo features:

  • limit_128
  • limit_256
  • limit_512
  • limit_1024
  • limit_2048

No runtime deps