3 ms·
I know this one hit quite a few people: https://github.com/rust-windowing/winit/issues/1773 https://github.com/rust-windowing/winit/issues/1773. Compiles on new
by edflsafoiewq 6y ago
I know this one hit quite a few people: https://github.com/rust-windowing/winit/issues/1773 https://github.com/rust-windowing/winit/issues/1773. Compiles on new rustc but panics at runtime. API churn also made upgrading to a new winit painful.
- pornel 6y agoUse of uninitialized memory is Undefined Behavior. So in a sense, that code never worked properly, but authors didn't know about it until Rust caught it explicitly.
- lima 6y agoAny observable behavior will be depended upon. A breaking change is a breaking change no matter what. Of course it's good that they fixed the UB.
- dralley 6y agoIt's undefined behavior. Anything can happen, by definition. I understand what you're saying, but anyone who knowingly relies on undefined behavior deserves whatever pain they get, and anyone who didn't know they were relying on undefined behavior, needed to know about it.