Tracking issue for release notes of #162927: stabilize ptr_cast_slice
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
Research direction
Read the linked release notes guide and the previous releases for category and wording examples, then review pull request #162927 to understand the stabilization. Edit the release notes section with the appropriate category and a concise description; consider whether compatibility notes or stabilized API headers are needed. Leave the release blog section empty unless the change merits a blog post.
Written by the indexing model from the issue text.
Description
This issue tracks the release notes text for #162927.
cc @malezjaa, @nia-e -- 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 APIsandConst Stabilized APIs?
# Language/Compiler/Libraries/Stabilized APIs/Const Stabilized APIs/Rustdoc/Compatibility Notes/Internal Changes/Other
- [stabilize ptr_cast_slice](https://github.com/rust-lang/rust/pull/162927)
[!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-postlabel 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
- 120k
- Forks
- 18.7k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 550
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from rust-lang/rust
-
relnotes relnotes-needs-review relnotes-tracking-issue T-compiler T-lang T-rustfmt
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
A-run-make A-testsuite relnotes relnotes-needs-review relnotes-tracking-issue T-bootstrap T-cargo T-compiler
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
innvalid `invalid_nan_comparisons breaks`: no method named `is_nan` found for reference `&{float}`Possibly taken @caelyreth claimed this 5 days ago. OpenA-diagnostics A-floating-point A-suggestion-diagnostics C-bug D-invalid-suggestion L-invalid_nan_comparisons T-compiler
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
relnotes relnotes-needs-review relnotes-tracking-issue T-compiler T-libs
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rust-lang/rust#163875 · 1 comment ·
Maintainers usually reply within 1 day
-
relnotes-tracking-issue T-release
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
rust-lang/rust#163811 · 5 comments ·
Maintainers usually reply within 1 day
Similar issues
-
area:ecosystem documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Chelis-Lang/chelis#3866 ·
Maintainers usually reply within 1 day
-
bug documentation sev-0
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dekobon/big-code-analysis#1620 ·
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100