Skip to content
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.

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

docs: Clarify FIFO Behavior of tokio::sync::Mutex #6279

Merged
merged 4 commits into from
Jan 11, 2024

Conversation

azuredream
Copy link
Contributor

@azuredream azuredream commented Jan 9, 2024

Closes: #6278

Signed-off-by: azuredream <zhaozixuan67@gmail.com>
@github-actions github-actions bot added the R-loom-sync Run loom sync tests on this PR label Jan 9, 2024
Signed-off-by: azuredream <zhaozixuan67@gmail.com>
@Darksonn Darksonn added T-docs Topic: documentation A-tokio Area: The main tokio crate M-sync Module: tokio/sync labels Jan 10, 2024
Copy link
Contributor

@Darksonn Darksonn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, a few suggestions.

@@ -17,6 +17,11 @@ use std::{fmt, mem, ptr};
/// differences: [`lock`] is an async method so does not block, and the lock
/// guard is designed to be held across `.await` points.
///
/// Please note that Tokio's Mutex operates on a guaranteed FIFO basis.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is redundant.

Suggested change
/// Please note that Tokio's Mutex operates on a guaranteed FIFO basis.
/// Tokio's Mutex operates on a guaranteed FIFO basis.

/// Please note that Tokio's Mutex operates on a guaranteed FIFO basis.
/// This means that the order in which tasks call the [`lock`] method is
/// the exact order in which they will acquire the lock.
/// We commit to maintaining this behavior in future versions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is generally implicit, so it's redundant to include it.

Suggested change
/// We commit to maintaining this behavior in future versions.

@azuredream
Copy link
Contributor Author

Updated. Thanks for your review!

Copy link
Contributor

@Darksonn Darksonn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.

@Darksonn Darksonn merged commit 8463af9 into tokio-rs:master Jan 11, 2024
71 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-tokio Area: The main tokio crate M-sync Module: tokio/sync R-loom-sync Run loom sync tests on this PR T-docs Topic: documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documentation of tokio::sync::Mutex needs to be clearer about the FIFO behavior
2 participants