Rust

5974 readers

14 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

Credits

The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)

founded 1 year ago

MODERATORS

[email protected]

"Clean" Code, Horrible Performance in Rust (chrs.dev)

submitted 7 months ago by [email protected] to c/[email protected]

26 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 7 months ago* (last edited 7 months ago)

So the problem discovered is that the compiler can't optimize the loops by unrolling them (due to floating point issues?). The proposed solution is to unroll the loop manually.

But wouldn't it be much cleaner and more performant to just have a macro like #![allow lossy floating point optimizations] and let the compiler figure out the rest?

Compilers exist to compile and optimize things. Manually unrolling loops might improve performance on one machine, but completely break the program on another. It's much safer and more performant in the long term to allow the compiler the leeway to optimize things the optimal way.