Jump to content

Inlining Gone Wrong: How Rust’s Optimizer Sometimes Betrays You: Revision history

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

22 November 2025

  • curprev 05:0205:02, 22 November 2025 PC talk contribs 9,060 bytes +9,060 Created page with "500px There’s a special kind of heartbreak every systems developer knows:
You open your profiler expecting to see your carefully tuned function blazing fast…
…and instead, it’s taking more time than before you optimized it. You didn’t change the algorithm. You just added #[inline(always)]. Welcome to the dark side of Rust’s inlining optimizer — where performance can sometimes regress the moment you try to help i..."
Retrieved from "https://johnwick.cc/index.php?title=Inlining_Gone_Wrong:_How_Rust’s_Optimizer_Sometimes_Betrays_You"