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 @burntsushi5
I'm wary about basing this on what versions ship with os distros since it takes that choice away from our community (even if it's relevant to things like eg ripgrep). Could argue that folks who can't upgrade compiler versions don't necessarily need the latest version of an app
3 replies 0 retweets 1 like -
Replying to @sgrif @burntsushi5
At the same time, I think we can all agree that libs only supporting latest stable is bad for the ecosystem. Foundational libs should probably be more conservative (realising you are one is hard. Is diesel a foundational lib?)
1 reply 0 retweets 1 like -
Replying to @sgrif @burntsushi5
And there is often serious benefit to bumping the min version. MaybeUninit is needed to avoid UB. Async/await enables code you can't otherwise write safely. How long to we hold those back?
1 reply 0 retweets 0 likes -
Replying to @sgrif
Yup. It's hard. A good step forward is to just to keep all this stuff in mind, and treat an MSRV bump as a trade off like anything else. Lots of folks don't do this, probably because the tooling just doesn't make it visible.
1 reply 0 retweets 1 like
Yeah, I agree. Diesel's policy is "we don't make guarantees about MSRV, but we promise we only bump for a good reason. E.g. if bumping is required to implement some feature or remove UB, not just for some convenience function", which seems reasonable for most libs
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.