Stabilisation of ARM AES intrinsics missing from 1.72 release notes
Open
Nobody has claimed this yet.
A-docs
O-Arm
T-libs
T-release
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Location
Both:
- https://blog.rust-lang.org/2023/08/24/Rust-1.72.0.html
- https://github.com/rust-lang/rust/releases/tag/1.72.0
Summary
If you go to https://doc.rust-lang.org/core/arch/aarch64/fn.vaesdq_u8.html that reports it was stabilised in 1.72. However, it is not mentioned in:
- https://blog.rust-lang.org/2023/08/24/Rust-1.72.0.html
- https://github.com/rust-lang/rust/releases/tag/1.72.0
Naturally I'm not expecting these to be altered post-hoc, but I feel there might be a process improvement here for ensuring stdarch changes are reflected in the release notes?
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
Review the Rust 1.72.0 blog post and GitHub release notes alongside the stdarch change that stabilized vaesdq_u8. Trace how stdarch stabilizations are surfaced in release notes, then document a concrete process improvement so future changes are included; done means the omission and proposed workflow are clearly recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100