4 ms·
No one discusses how with new releases old code breaks. I can compile C code from 40 years ago. I can't compile code in Rust I wrote from 4 months ago. I feel R
by deviantbit 3y ago
No one discusses how with new releases old code breaks. I can compile C code from 40 years ago. I can't compile code in Rust I wrote from 4 months ago. I feel Rust will always be a moving target. I am getting very discouraged.
- MrJohz 3y agoRust has fairly strong backwards-compatibility guarantees, so that sort of claim surprises me. Can you give an example of the code you wrote four months ago that won't compile using the latest stable toolchain?
- sgift 3y agoIf you only used stable rust (i.e. not nightly) I would be interested in an example of code you wrote 4 month ago that you cannot compile anymore.
- vlovich123 3y agoDon’t use rust nightly. Is there any indication that code built against Rust 1.0 no longer works?
- Asraelite 3y agoI remember seeing a fix that was introduced which was technically a breaking change to stable, but only in obtuse edge cases nobody actually used. The entirety of crates.io still compiled. So breakages can in theory happen but yeah I don't think they do in practice.
- treyd 3y agoThis isn't really true with stable Rust. Rust uses a system of "editions" for crates, where newer compilers are directed to parse the code using the older rules and it can freely interoperate with code written for newer editions even in the same binary. If you use nightly features then sure, that can break, but once a feature is stabilized its functionality is guaranteed for many years.
- logankeenan 3y agoI’d be interested in an example of Rust code that worked 4 months ago and now does not work.
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- ketralnis 3y ago> I can't compile code in Rust I wrote from 4 months ago What code? I have never observed this