News for hackers. Stuff that matters.

A comment on Rust 1.x seems to not always be backward compatible in practice. Parent comment

Re:Rust 1.x seems to not always be backward compatible in pr... by zxzax on Sunday June 13, 2021 @10:10AM (#27492749)
I don't see how that's different to C++. You will run into the same issues there if you happen to use code that uses some of the various new features e.g. items targeted for C++23, that are already starting to be supported by the newest versions of GCC and Clang. If you're on Debian Stable or RHEL, I believe those are even still using GCC versions that don't fully support C++20.
[ Parent | on HN ]
Re:Rust 1.x seems to not always be backward compatible in pr... by steveklabnik on Sunday June 13, 2021 @10:16AM (#27492795)
Their argument is a cultural one, not a technical one. Technically, they’re the same, but culturally, C++XY takes time to see adoption, but Rust 1.Y tends to be adopted almost immediately.
[ Parent | on HN ]
Re:Rust 1.x seems to not always be backward compatible in pr... by zxzax on Sunday June 13, 2021 @10:19AM (#27492827)
On certain corners of Github, I wouldn't say so. I think you would see a lot more people doing the same thing in C++, if there was a Cargo-style package manager that got more adoption there.
[ Parent | on HN ]