New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking issue for integer_atomics #99069
Comments
Updates rust-lang#32976. Updates rust-lang#99069.
…fJung Update integer_atomics tracking issue Updates rust-lang#32976. Updates rust-lang#99069. r? `@RalfJung`
…fJung Update integer_atomics tracking issue Updates rust-lang#32976. Updates rust-lang#99069. r? ``@RalfJung``
It'd be good to list the APIs that are covered by this tracking issue, and copy any open questions that have been noted in the RFC of the previous tracking issue. |
Updates rust-lang#32976. Updates rust-lang#99069.
…fJung Update integer_atomics tracking issue Updates rust-lang#32976. Updates rust-lang#99069. r? ``@RalfJung``
The unstable |
The standard library docs for |
What do you mean? Interestingly, in the online documentation the types don't show up at all, whereas they do show up in my local copy ( |
Apologies, I must have accidentally followed a link to somebody else's stale docs. |
the trait bound |
…=Amanieu remove the unstable `core::sync::atomic::ATOMIC_*_INIT` constants Tracking issue: rust-lang#99069 It would be weird to ever stabilise these as they are already deprecated.
Now that #120820 has been merged, there are multiple T1 targets that support 128-bit atomics: as well as a few lower-tier targets such as |
Tracking rust-lang/rfcs#1543.
Seems related to #56071. See also #57425 which stabilized other atomic integer widths.
The text was updated successfully, but these errors were encountered: