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

Abierto
  • ¿Algo no está bien?
#165,433 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Área
documentation, release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
121k
Forks
17.3k
Merge medio
2 d 21 h
PR fusionados (30 d)
531

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de rust-lang/rust

Todos los issues de rust-lang/rust

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.