the most compelling argument i've seen here is that this is a frustrating hurdle for new users who, quite reasonably, expect that they can/should install the compiler toolchain via their package manager like yeah it's the distro's fault, but that doesn't matter?
-
-
I agree with you that crate authors shouldn't refrain from using new Rust features in order to remain compatible with LTS rustc/cargo. What's your take on whether requiring newer Rust should be treated as semver "breaking", though?https://users.rust-lang.org/t/rust-version-requirement-change-as-semver-breaking-or-not/20980 …
-
I am pretty liberal about bumping the "incompatible version" number of my crates. Generally I bump it when I think I've probably made a change that requires a new version of Rust. But since I don't test on older versions of the toolchain IDK how good I am at guessing.
End of conversation
New conversation -
-
-
I don't think it's reasonable to expect users to install anything except through their OS's package manager. That's how malware spreads. Languages that make proper packaging difficult should be boycotted by developers.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.