Tracking Issue for `hint_prefetch`
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(hint_prefetch)]
This is a tracking issue for hints to prefetch memory.
Public API
// core::hint
#[non_exhaustive]
pub enum Locality {
L3,
L2.
L1,
}
pub const fn prefetch_read<T>(ptr: *const T, locality: Locality);
pub const fn prefetch_write<T>(ptr: *mut T, locality: Locality);
pub const fn prefetch_read_non_temporal<T>(ptr: *const T, locality: Locality);
pub const fn prefetch_write_non_temporal<T>(ptr: *mut T, locality: Locality);
pub const fn prefetch_read_instruction<T>(ptr: *const T, locality: Locality);
Steps / History
(Remember to update the S-tracking-* label when checking boxes.)
- ACP https://github.com/rust-lang/libs-team/issues/638
- #146948
- Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
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 with the proposed core::hint API and review the completed ACP and #146948 linked in the tracking issue. Check the feature lifecycle requirements for the remaining Final Comment Period and stabilization PR steps. Done means the unresolved stabilization work is completed and the tracking checklist is updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100