Rollup merge of #121977 - Lee-Janggun:master, r=WaffleLapkin

Doc: Fix incorrect reference to integer in Atomic{Ptr,Bool}::as_ptr.

I am assuming "resulting integer" is an error, since we are talking about pointers and booleans here. Seems like it was missed while copy & pasting the docs from the integer versions. I also checked the rest of the docs, and this was the only mention of integers.
This commit is contained in:
Matthias Krüger 2024-03-04 22:16:34 +01:00 committed by GitHub
commit c83ca5ba9a
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -1092,7 +1092,7 @@ impl AtomicBool {
/// Returns a mutable pointer to the underlying [`bool`].
///
/// Doing non-atomic reads and writes on the resulting integer can be a data race.
/// Doing non-atomic reads and writes on the resulting boolean can be a data race.
/// This method is mostly useful for FFI, where the function signature may use
/// `*mut bool` instead of `&AtomicBool`.
///
@ -2031,7 +2031,7 @@ impl<T> AtomicPtr<T> {
/// Returns a mutable pointer to the underlying pointer.
///
/// Doing non-atomic reads and writes on the resulting integer can be a data race.
/// Doing non-atomic reads and writes on the resulting pointer can be a data race.
/// This method is mostly useful for FFI, where the function signature may use
/// `*mut *mut T` instead of `&AtomicPtr<T>`.
///