Tracking issue for release notes of #157973: Distinguish `repr(C)` ZSTs from others in ABI compatibility rules
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust
- Domain
- documentation, release
Research direction
Read the release-notes guidance and inspect PR #157973 to understand the change and choose the appropriate release-note category. Compare the wording with previous releases, then replace the placeholder entry with a succinct description; add a release blog section only if the change is notable enough.
Written by the indexing model from the issue text.
Description
This issue tracks the release notes text for #157973.
cc @Jules-Bertholet, @CAD97 -- 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
- [Distinguish `repr(C)` ZSTs from others in ABI compatibility rules](https://github.com/rust-lang/rust/pull/157973)
[!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
- 119k
- Forks
- 16.2k
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 550
Getting set up
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
-
A-const-generics A-diagnostics F-gca_min_const_items T-compiler
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
rust-lang/rust#163478 · 2 comments ·
Maintainers usually reply within 1 day
-
C-discussion
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rust-lang/rust#163468 · 6 comments · 5 reactions ·
Maintainers usually reply within 1 day
-
relnotes relnotes-tracking-issue T-bootstrap T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
release-blog-post relnotes relnotes-tracking-issue T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-triage relnotes relnotes-tracking-issue T-clippy T-libs
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Automattic/harper#4503 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 2 days