Brainstorm with me. How plausible is it for quickcheck to break ties with rand?https://github.com/BurntSushi/quickcheck/issues/241 …
-
-
Replying to @burntsushi5
Commenting here since it's tangential, and I don't want to derail your issue, but I think we really need to decide as a community what we consider to be the norm for compiler version support. I think we can be more aggressive than other langs, but different crates have diff needs
3 replies 0 retweets 10 likes -
Replying to @sgrif
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.
1 reply 0 retweets 7 likes -
Replying to @burntsushi5
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
2 replies 0 retweets 5 likes -
Replying to @sgrif @burntsushi5
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.
2 replies 1 retweet 8 likes -
Replying to @BRIAN_____ @sgrif
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.
2 replies 0 retweets 0 likes -
I don't like LTS releases for the same reason I didn't like--and fought against--Firefox's ESR (and was ultimately forced to do it). Takes resources from present and future to accommodate people stuck in the past. Codifies bad practices as accepted and encouraged
3 replies 5 retweets 15 likes
I don't like LTS for the same reason too. I run a rolling release Linux distro because of that. But that's my personal taste. When my libraries have a lot of users, I want to be conservative where possible, and avoid introducing churn.
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.