Brainstorm with me. How plausible is it for quickcheck to break ties with rand?https://github.com/BurntSushi/quickcheck/issues/241 …
-
I agree. To be clear though, if it were only about MSRV, I could overlook that, at least for rand. I still like the LTS idea that boats/aturon proposed. It provides a rallying point. Adding MSRV to Cargo.toml in order to improve failure modes is also a good start.
LTS RFC is definitely the most compelling solution I've seen so far. I also agree adding this to Cargo.toml would be great, especially if it affected version resolution
-
-
How’d crate maintainers be compensated ($) for maintaining an LTS version that’s no fun, only pain? There’s no plan for that, AFAICT, making the whole LTS idea accidentally anti-maintainer & pro-freeloading, despite good intentions. “Latest stable Rust only” works economically.
-
I don't work in crypto. I'm happy to have crypto people tell me the policy doesn't work for them. But that doesn't mean it others can't or shouldn't adopt it.
- 7 more replies
New conversation -
-
-
With MSRV in version resolution we can have the cake and eat it too. I'm not going to support LTS Rust versions in crates I publish, and will only end up having spats with angry LTS users I'll break. With MSRV it all works, for everyone, automatically.
-
I think it would be fine to not adhere to LTS if there was one. But it would also be fine for others to use that criteria in determining http://whether.to use that crate or not. If there was an LTS, it is unlikely that i would even target it for all my crates.
End of conversation
New conversation -
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.