Skip to content

Clarify how MutexGuard is 'thread-safe' (avoiding the vague term) #2336

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.

Sign up for GitHub

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

Merged
djmitche merged 1 commit into from
Sep 3, 2024
Merged

Clarify how MutexGuard is 'thread-safe' (avoiding the vague term) #2336

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/concurrency/send-sync/examples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,12 @@ Typically because of interior mutability:

## `!Send + Sync`

These types are thread-safe, but they cannot be moved to another thread:
These types are safe to access (via shared references) from multiple threads,
but they cannot be moved to another thread:

- `MutexGuard<T: Sync>`: Uses OS level primitives which must be deallocated on
the thread which created them.
the thread which created them. However, an already-locked mutex can have its
guarded variable read by any thread with which the guard is shared.

## `!Send + !Sync`

Expand Down