Tracking issue for release notes of #143343: Lint against `&T` to `&mut T` and `&T` to `&UnsafeCell<T>` transmutes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
This issue tracks the release notes text for #128351, rebased in #143343.
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, ...)
- [Lint against `&T` to `&mut T` and `&T` to `&UnsafeCell<T>` transmutes](https://github.com/rust-lang/rust/pull/128351)
[!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 @ChayimFriedman2, @GrigorenkoPV, @wesleywiser -- origin issue/PR authors and assignees for starting to draft text
Contributor 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.
Research direction
Start by reading PR #128351 and its rebased PR #143343 to understand the lint change. Replace the generated link in the Release notes text section with a succinct description, choose an appropriate category using previous releases, and leave the blog section empty unless the change is notable enough for it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100