Anyone who does `cargo run`. A project I'm working on right now is slow enough in debug builds that I usually debug it with light optimizations enabled. Lean on the optimizer and you'll find it a leaky abstraction.
The entire discussion starts from looking at getting bounds checks optimised away, not optimising seems counter-productive to this concern?
> lean on the optimiser and you’ll find it a leaky abstraction.
The abstraction here is not really leaky though, observable behaviour would be as expected t’es, it’s when you look at his this behaviour is achieved that things start looking odd.
> The entire discussion starts from looking at getting bounds checks optimised away, not optimising seems counter-productive to this concern?
I'm aware of the history of the conversation, but the point where I joined concerned which idiom performs better unoptimized, a case which is relevant because everybody cargo-runs.
> The abstraction here is not really leaky though, observable behaviour would be as expected t’es, it’s when you look at his this behaviour is achieved that things start looking odd.
In many circumstances performance is part of observable behavior.
> Yeah but who'd do that?
Anyone who does `cargo run`. A project I'm working on right now is slow enough in debug builds that I usually debug it with light optimizations enabled. Lean on the optimizer and you'll find it a leaky abstraction.