Brainstorm with me. How plausible is it for quickcheck to break ties with rand?https://github.com/BurntSushi/quickcheck/issues/241 …
-
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
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
-
-
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?)
-
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?
- 2 more replies
New conversation -
-
-
For apps, I don't care much abut MSRV. In that case, I'm okay with just building an older version. This is harder to do with libraries though, because everything is intertwined and distros only want to package one version of a library (AFAIK). See also:https://github.com/BurntSushi/ripgrep/issues/1019 …
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Agree with this because once more crates hit the 1.0 release, compiler versions supported will be a crucial issue for most of them
-
I think very few libraries consider this a crucial issue and that's part of the problem.
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.