File tree Expand file tree Collapse file tree 2 files changed +3
-3
lines changed Expand file tree Collapse file tree 2 files changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -575,7 +575,7 @@ impl<T> Channel<T> {
575
575
// After this point `head.block` is not modified again and it will be deallocated if it's
576
576
// non-null. The `Drop` code of the channel, which runs after this function, also attempts
577
577
// to deallocate `head.block` if it's non-null. Therefore this function must maintain the
578
- // invariant that if a deallocation of head.block is attemped then it must also be set to
578
+ // invariant that if a deallocation of head.block is attempted then it must also be set to
579
579
// NULL. Failing to do so will lead to the Drop code attempting a double free. For this
580
580
// reason both reads above do an atomic swap instead of a simple atomic load.
581
581
Original file line number Diff line number Diff line change @@ -32,7 +32,7 @@ pub fn enable() {
32
32
33
33
/// On platforms with key-based TLS, the system runs the destructors for us.
34
34
/// We still have to make sure that [`crate::rt::thread_cleanup`] is called,
35
- /// however. This is done by defering the execution of a TLS destructor to
35
+ /// however. This is done by deferring the execution of a TLS destructor to
36
36
/// the next round of destruction inside the TLS destructors.
37
37
#[ cfg( not( target_thread_local) ) ]
38
38
pub fn enable ( ) {
@@ -46,7 +46,7 @@ pub fn enable() {
46
46
unsafe extern "C" fn run ( state : * mut u8 ) {
47
47
if state == DEFER {
48
48
// Make sure that this function is run again in the next round of
49
- // TLS destruction. If there is no futher round, there will be leaks,
49
+ // TLS destruction. If there is no further round, there will be leaks,
50
50
// but that's okay, `thread_cleanup` is not guaranteed to be called.
51
51
unsafe { set ( CLEANUP . force ( ) , RUN ) }
52
52
} else {
You can’t perform that action at this time.
0 commit comments