this post was submitted on 31 Aug 2023
105 points (94.1% liked)

Rust

5980 readers
81 users here now

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

Wormhole

!performance@programming.dev

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
snowe@programming.dev
Ategon@programming.dev
EdTheLegendary@programming.dev
kahnclusions@programming.dev
torcherist@programming.dev
105
Why Rust is the most admired language among developers? (github.blog)
submitted 1 year ago by starman@programming.dev to c/rust@programming.dev
43 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[โ€“] teolan@lemmy.world 2 points 1 year ago (1 children)

The only time it has ever complained was a case where my platform does define the behavior and I was intentionally relying on that.

If by platform you mean target CPU you should be aware that it's still undefined behaviour and that it could break optimizations, unless your compiler also makes a commitment to define that behavior that is stronger than what the standard requires.

[โ€“] bluGill@kbin.social 1 points 1 year ago

I broke the one definition rule by having a symbol in two different .so files. The optimizer can't optimize around this and on Linux the order of loading says who wins. On windows there are different rules, but I forget which.

Of course if the optimizer could make an optimization I would be in trouble, but my build systems ensures that there is no optimizer that gets access to either definition.