Re:A half-hour to learn Rust
by gpm on Saturday January 02, 2021 @03:20PM
(#25616102)
My housemate was just rolling back from python 3.8 to 3.7 yesterday due to a backwards incompatible change breaking a library... it's not just 2 -> 3 that makes python relatively unstable compared to rust.
[ Parent
| on HN ]
Yup, similar is 3.5->3.7. The community also doesn't seem to value backwards-compatiblity, judging from the libraries.
And I recently had to roll back from Python 3.9 to 3.7 to work around a couple different problems with the cffi and zstandard libraries on macOS 11.
Re:A half-hour to learn Rust
by indolering on Tuesday January 05, 2021 @12:24AM
(#25642431)
How does library breakage reflect on Rust? Python's deprecation policy is 2 years, only a year less than that of Rust's Epoch system.
Epoch's don't break libraries - that's the whole point.
They manage this by allowing using a different epoch in a library than the application that uses it, and defaulting to the original epoch if you don't ask to use a new one.
The vast majority of rust 1.0 libraries should still work with modern rust programs, I vaguely recall that there was one minor backwards incompatible change as of a result of memory safety bug (an exception to the guarantee), but I can't remember what it was and I can't find it with google so it might actually be all rust 1.0 libraries still work.
Re:A half-hour to learn Rust
by alexanderdmitri on Saturday January 02, 2021 @04:11PM
(#25616578)
What the issue?