Skip to content

Tracking Issue for const_volatile #159094

Open

Description

@RalfJung

Feature gate: #![feature(const_volatile)]

This is a tracking issue for volatile operations in const.

Public API

// core::ptr

pub const unsafe fn read_volatile<T>(src: *const T) -> T;
pub const unsafe fn write_volatile<T>(dst: *mut T, src: T);

impl<T> *const T {
  pub const unsafe fn read_volatile(self) -> T;
}

impl<T> *mut T {
  pub const unsafe fn read_volatile(self) -> T;
  pub const unsafe fn write_volatile(self, val: T);
}

impl<T> NonNull<T> {
  pub const unsafe fn read_volatile(self) -> T;
  pub const unsafe fn write_volatile(self, val: T);
}

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

Unresolved Questions

  • None yet.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩

Activity

  1. added
    T-libs-api[DEPRECATED; DO NOT USE]
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Jul 10, 2026
  2. added 2 commits that reference this issue on Jul 10, 2026
  3. added a commit that references this issue on Jul 11, 2026
  4. added a commit that references this issue on Jul 11, 2026
  5. maxdexh commented on Jul 25, 2026

    @maxdexh
  6. RalfJung commented on Jul 25, 2026

    @RalfJung
    Author
  7. RalfJung commented on Jul 28, 2026

    @RalfJung
    MemberAuthor

    Cc @rust-lang/libs-api just to make sure you are aware of this :)

  8. added 3 commits that reference this issue on Aug 1, 2026
  9. added a commit that references this issue on Aug 1, 2026
  10. added
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    and removed
    T-libs-api[DEPRECATED; DO NOT USE]
    on Aug 12, 2026
  11. added a commit that references this issue on Oct 10, 2026
  12. added a commit that references this issue on Oct 10, 2026
  13. added a commit that references this issue on Oct 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.T-libsRelevant to the library team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions