The biggest threat to Rust's sustainability

Re:The biggest threat to Rust's sustainability by juergbi on Friday March 19, 2021 @05:43AM (#26511520)

> 1. Rust has very strong stability guarantees. If you want to you can continue coding like it's Rust 1.0 even on the latest compiler.

There have been at least two cases where Firefox build broke due to having a too recent version of Rust installed. The stability guarantees may be fairly strong but it's definitely not perfect.

[ Parent | on HN ]

Re:The biggest threat to Rust's sustainability by ChrisSD on Friday March 19, 2021 @05:45AM (#26511534)

Sorry, I didn't mean to imply it's bug-for-bug compatible with Rust 1.0. The language however is the same.

[ Parent | on HN ]

Re:The biggest threat to Rust's sustainability by edflsafoiewq on Friday March 19, 2021 @05:55AM (#26511592)

I know this one hit quite a few people: 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.

[ Parent | on HN ]

Re:The biggest threat to Rust's sustainability by pornel on Friday March 19, 2021 @06:11AM (#26511692)

Use 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.

[ Parent | on HN ]

Re:The biggest threat to Rust's sustainability by lima on Friday March 19, 2021 @07:31AM (#26512098)

Any 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.

[ Parent | on HN ]

Re:The biggest threat to Rust's sustainability by dralley on Friday March 19, 2021 @02:48PM (#26516993)

It'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.

[ Parent | on HN ]