Tracking issue for release notes of #164258: clarify when `Vec::into_boxed_slice()` is in-place

Open
  • Is something wrong?
#165,433 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
Under an hour
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
documentation, release

Research direction

The work is the release notes text in the issue body, which summarizes PR #164258 about Vec::into_boxed_slice() in-place behavior. Read that PR's diff and description to confirm what changed, then pick the correct category from the template, such as Libraries or Compatibility Notes. Done means a one-line entry in the template, checked with the release team's notes guidelines in the forge.rust-lang.org release-notes chapter.

Written by the indexing model from the issue text.

Description

relnotes relnotes-needs-review relnotes-tracking-issue T-libs

This issue tracks the release notes text for #164258.

cc @folkertdev, @JohnTitor -- original issue/PR authors and assignees for drafting text

See the forge.rust-lang.org chapter about release notes for an overview of how the release team makes use of these tracking issues.

Release notes text

This section should be edited to specify the correct category(s) for the change, with succinct description(s) of what changed. Some things worth considering:

  • Does this need an additional compat notes section?
  • Was this a libs stabilization that should have additional headers to list new APIs under Stabilized APIs and Const Stabilized APIs?
# Language/Compiler/Libraries/Stabilized APIs/Const Stabilized APIs/Rustdoc/Compatibility Notes/Internal Changes/Other
- [clarify when `Vec::into_boxed_slice()` is in-place](https://github.com/rust-lang/rust/pull/164258)

[!TIP]
Use the previous releases for inspiration on how to write the release notes text and which categories to pick.

Release blog section

If this change is notable enough for inclusion in the blog post then this section should be edited to contain a draft for the blog post. Otherwise leave it empty.

[!NOTE]

If a blog post section is required the release-blog-post label should be added (@rustbot label +release-blog-post) to this issue as otherwise it may be missed by the release team.

Dominant language
Rust
Stars
121k
Forks
17.3k
Avg merge
2d 21h
Merged PRs (30d)
531

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rust-lang/rust

All issues in rust-lang/rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.