rust-lang / rust-lang/rust

Tracking issue for release notes of #133820: Stabilize `derive(CoercePointee)`

Open
#134,624 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

F-derive_coerce_pointee relnotes relnotes-tracking-issue T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This issue tracks the release notes text for #133820.

Steps
  • Proposed text is drafted by PR author (or team) making the noteworthy change.
  • Issue is nominated for release team review of clarity for wider audience.
  • Release team includes text in release notes/blog posts.
Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Stabilize `derive(CoercePointee)`](https://github.com/rust-lang/rust/pull/133820) ([RFC](https://rust-lang.github.io/rfcs/3621-derive-smart-pointer.html))

[!TIP]
Use the previous releases categories to help choose which one(s) to use.
The category will be de-duplicated with all the other ones by the release team.

More than one section can be included if needed.

Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
Otherwise leave it empty.

cc @dingxiangfei2009, @joboet -- origin issue/PR authors and assignees for starting to draft text

Contributor guide

Open the contributing guide

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.

Research direction

Read PR #133820 and the linked RFC 3621, then review the previous releases for suitable categories. Replace the generated link in the Release notes text section with a succinct description and category; add blog content only if the change is notable enough, otherwise leave that section empty.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
documentation, release
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.