File tree Expand file tree Collapse file tree 2 files changed +2
-2
lines changed Expand file tree Collapse file tree 2 files changed +2
-2
lines changed Original file line number Diff line number Diff line change 733733//! sensitivity, it will need to be structurally pinned.
734734//!
735735//! A useful test is if [`unsafe`] code that consumes <code>[Pin]\<[&mut Struct][&mut]></code>
736- //! also needs to take note of the address of the field itself, it may be evidence that that field
736+ //! also needs to take note of the address of the field itself, it may be evidence that field
737737//! is structurally pinned. Unfortunately, there are no hard-and-fast rules.
738738//!
739739//! ### Choosing pinning *not to be* structural for `field`...
Original file line number Diff line number Diff line change @@ -136,7 +136,7 @@ cfg_if!(
136136 // match do we read out the actual TID.
137137 // Note also that we can use relaxed atomic operations here, because
138138 // we only ever read from the tid if `tls_addr` matches the current
139- // TLS address. In that case, either the the tid has been set by
139+ // TLS address. In that case, either the tid has been set by
140140 // the current thread, or by a thread that has terminated before
141141 // the current thread was created. In either case, no further
142142 // synchronization is needed (as per <https://github.com/rust-lang/miri/issues/3450>)
You can’t perform that action at this time.
0 commit comments