The 1.27.1 release will be made on Tuesday, July 10th. This includes the security fix for rustdoc and a patch for match ergonomic potential unsoundness.
Please test this release out by running RUSTUP_DIST_SERVER=https://dev-static.rust-lang.org rustup update stable; the artifacts are at https://dev-static.rust-lang.org/dist/2018-07-08/index.html.
Release notes can be found on GitHub.
You surely mean July, not April.
I’m guessing it’s supposed to be July 10?
I won’t lie. The number of x.1 releases with soundness fixes recently makes me uncomfortable. Perhaps we’re putting new features out too quickly?
More than the pace of new features, I think what would be interesting is what happened to let us find those soundness issue after release (leading to a .1), and why didn’t it happen during nightly or beta? And were those issues introduced in the .0 of the same cycle, or had they been present for several cycles and we don’t bother to patch before the current Stable?
My guess: Because people only turn on the features they are actively using. For ergonomics features, that tends to be just people who are testing the feature because nobody “needs” them per se; that is, they’re great to have, but I can get my program working without it.
For example, I didn’t use match default bindings before it was on stable, but I did use global_allocator and panic_implementation.
Perhaps the solution is to allow some features to be turned on by default (on nightly only) for some time before we intend to stabilize but after we think the feature is debugged enough. Of course, the tradeoff is that would make nightly programs more likely to be buggy/more likely to experience breakage, but after all, it is nightly…
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.