Rationale
Why the compiler is on this page
The language keeps a parser out of production bundles. This site loads one deliberately.
Why is the compiler on this page, when the language says it must not ship?
Because the rule is about production bundles and this is not one. The language keeps a parser out of a consumer's application through a separate entry point and a size gate that fails when the parser turns up in a runtime-only build. A playground is the one application whose product is compilation, so it loads the parser on purpose.
Which is exactly why it is worth saying
A site that quietly did this and let the language's own claim stand elsewhere on the page would be trading on a rule it was breaking. The separation is real, it is enforced by a fixture rather than a promise, and this page is the documented exception rather than a hole in it.
// Overflow says which kind it is. A health bar saturates rather than wrapping to zero.
fn health(current: u8, healed: u8) -> u8 {
return current +| healed
}
What it costs here
The compiler arrives on the first press rather than on load, so a reader who scrolls past every box pays nothing, and a reader who presses one waits for a chunk. That is the trade, and the figures for it are on the front page, measured by the build that published this.