Rust 1.41.0 announcement

[pietroalbini]

Mainly by me and @Centril.

cc @rust-lang/core @rust-lang/release

[rust-highfive]

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

[CryZe]

What about overriding the build settings of dependencies? That's like the biggest feature of 1.41 for me and it seems absent here.

[pietroalbini]

@CryZe announcement blog posts never contain the full set of changes in a release, but a small amount of highlights the release team thinks are interesting to a large amount of users.

[CryZe]

Yeah I agree, but not pointing that out and instead pointing out minor things like Box being FFI compatible (which is funny, cause I was the one pushing for Box being FFI compatible) is kind of weird. The cargo changes (also the docs documenting private items now) are much more useful to "the common developer" than obscure FFI things that only a minority of people will ever use. Being able to boost the performance of dependencies is huge for pretty much everyone working on games or other performance critical code that is way too slow to be executed in the debug profile at the moment. So I very much disagree with not mentioning that at all.

Maybe even just a small section that just talks about cargo having gained other features, such as support for documenting private items and changing the build settings of dependencies without going too deep into it would be fine.

[steveklabnik]

Release blog posts used to have a whole Cargo section, which is now apparently relegated to a link to its changelog.

[Mark-Simulacrum]

To be clear, this was not (at least on my part) an intentional decision; I was simply not aware that this was shipping in this release. I may try to fit it in if I have time between now and the release, but I don't think that's likely to happen.

We sometimes have a Cargo section, and sometimes don't -- it varies based on what is deemed important. I think this cycle we were all pretty strapped on time and less effort/review than usual went into the blog post, too (edit: at least on my part).