Skip to content

Commit fbcd2f5

Browse files
committed
tidy. Again
1 parent fe557ee commit fbcd2f5

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/libcore/cell.rs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1167,7 +1167,7 @@ impl<'a, T: ?Sized + fmt::Display> fmt::Display for RefMut<'a, T> {
11671167
/// feature to work around this restriction. All other types that allow internal mutability, such as
11681168
/// `Cell<T>` and `RefCell<T>` use `UnsafeCell` to wrap their internal data.
11691169
///
1170-
/// The `UnsafeCell` API itself is technically very simple: it gives you a raw pointer `*mut T` to
1170+
/// The `UnsafeCell` API itself is technically very simple: it gives you a raw pointer `*mut T` to
11711171
/// its contents. It is up to _you_ as the abstraction designer to use that raw pointer correctly.
11721172
///
11731173
/// The precise Rust aliasing rules are somewhat in flux, but the main points are not contentious:
@@ -1182,7 +1182,7 @@ impl<'a, T: ?Sized + fmt::Display> fmt::Display for RefMut<'a, T> {
11821182
/// that reference expires.
11831183
///
11841184
/// - At all times, you must avoid data races, meaning that if multiple threads have access to
1185-
/// the same `UnsafeCell`, then any writes must have a proper happens-before relation to all other
1185+
/// the same `UnsafeCell`, then any writes must have a proper happens-before relation to all other
11861186
/// accesses (or use atomics).
11871187
///
11881188
/// To assist with proper design, the following scenarios are explicitly declared legal

0 commit comments

Comments
 (0)