Alex Portland

I tested the parallelization change introduced in #4236 on the workflow above, and it seems to improve the compile time of `prost` by 45%! Note that the baseline for my...

Hi! I'd be interested in taking a stab at adding some of these lints. Do you have suggestions on which one(s) would be best for me to start with?

I also ran this workflow on an old, slightly performance-regressing PR (#3374), and it successfully detects the small regression with [this output](https://github.com/AlexanderPortland/kani/blob/recreate-artems-branch/results.md).

@carolynzech I've added an additional `compiler-timing-long` job that runs on all the `s2n-quic` harnesses and takes about ~90s for each full compilation run (compared to the `-short` job which only...

[Here's](https://github.com/AlexanderPortland/kani/actions/runs/15766783026) the link to the newest CI run on my branch that has updated significance thresholds and small formatting changes. Should be finally ready for review now!

It seems that the issue is the internal use of the `core::panic!()` macro in `unwrap_failed()`. When a crate uses `panic!()` directly, the Kani compiler builds it with an `--extern` flag...

@zhassan-aws I just added a test that runs `kani` on three of the `panic!()` examples from above and checks to make sure that the emitted MIR properly contains our panic...

Hey @tautschnig, would this be best as a CI job (similar to the compiler timing one) or a regression test with a certain cache hit rate hard coded to detect...

Hey @tautschnig! Sorry for the delay, classwork is picking up and I just got sick lol. I did the fxhash change and I'll likely have a free day to sit...