4 ms·

I'm eagerly awaiting the Cargo feature "named profiles"[1]. It's already merged, but not yet announced to be planned for any specific Cargo version. It will all

I'm eagerly awaiting the Cargo feature "named profiles"[1]. It's already merged, but not yet announced to be planned for any specific Cargo version. It will allow users to create custom profiles with different build parameters from the standard ones, so you can e.g. create a "profiling" profile which is based on the "release" profile, so that it has all the nice optimizations, but with debug information included, so that it works well with cargo-flamegraph: [profile.profiling] inherits = "release" debug = true [1]: <https://github.com/rust-lang/cargo/pull/9943 https://github.com/rust-lang/cargo/pull/9943> And then there's the less fireworky, but still appreciated, Iterator::map_while[2], which is going to be in Rust 1.57. [2]: <https://github.com/rust-lang/rust/pull/89086 https://github.com/rust-lang/rust/pull/89086>

steveklabnik 5y ago
Unless something is special about this feature, new features generally aren't "planned" for specific versions in general. Since this landed two weeks ago, that means that it should land in the beta version of Cargo once that branches for this release (I didn't check if it has yet or not), which would place it to be stable in the next release of Rust, 1.57.0.
- yakubin 5y ago
  Thanks for the clarification. I just went by what's specified in the sidebar on GitHub in the "Milestone" section.
  - steveklabnik 5y ago
    Any time. Cargo doesn't use the Milestone feature of GitHub at all, so that's why that's empty :)
- lfairy 5y ago
  BTW, this article explains how Rust releases work: https://doc.rust-lang.org/book/appendix-07-nightly-rust.html https://doc.rust-lang.org/book/appendix-07-nightly-rust.html It's a release train, similar to that used by Chromium and Firefox. Edition releases (e.g. Rust 2021) are reserved for breaking changes only, and to retain Rust's stability promise, are opt-in.

steveklabnik 5y ago

Unless something is special about this feature, new features generally aren't "planned" for specific versions in general. Since this landed two weeks ago, that means that it should land in the beta version of Cargo once that branches for this release (I didn't check if it has yet or not), which would place it to be stable in the next release of Rust, 1.57.0.

yakubin 5y ago
Thanks for the clarification. I just went by what's specified in the sidebar on GitHub in the "Milestone" section.
- steveklabnik 5y ago
  Any time. Cargo doesn't use the Milestone feature of GitHub at all, so that's why that's empty :)
lfairy 5y ago
BTW, this article explains how Rust releases work: https://doc.rust-lang.org/book/appendix-07-nightly-rust.html https://doc.rust-lang.org/book/appendix-07-nightly-rust.html It's a release train, similar to that used by Chromium and Firefox. Edition releases (e.g. Rust 2021) are reserved for breaking changes only, and to retain Rust's stability promise, are opt-in.