Ever wondered why Cargo selects the *newest* versions of crates? Or what that might have to do with putting compiler versions in Cargo.toml? Well I have just the blog post for you: 
http://aturon.github.io/2018/07/25/cargo-version-selection/ …
-
Say more? I realize there are caveats, but this is a major part of the work the Release Team does on a regular basis.
I think it's misleading to say "the entire http://crates.io ecosystem" when it doesn't even include the 10 most downloaded crates. Anything that: - Is windows specific - Requires at least one feature enabled - Requires system libraries is not tested.
-
-
I believe that the testing harness is set up with some special configuration for crates that require system libraries. I'm not sure what you mean about enabling features -- are there critical crates that literally don't work with the default feature set? Windows point is legit.
-
None of diesel_cli, diesel_infer_schema, or diesel_migrations work without a feature enabled
- 16 more replies
New conversation -
-
-
I've been generally worried in the past that we put too much faith in a green crater run, treating it as a tool that says "yes this definitely does not break things" when all it can do is tell you "yes this definitely *does* break things", but not the opposite.
-
In my personal opinion, wording like that strengthens that false trust. Note: I am not trying to diminish crater's usefulness as a tool. It's incredibly powerful and I'm glad that we have it and use it as frequently as we do. Made some similar points in https://github.com/rust-lang-nursery/crater/pull/276 …
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.