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.

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

Jump to bottom

Mutex fairness policy #90

Closed
fvasco opened this issue Jul 26, 2017 · 3 comments
Closed

Mutex fairness policy #90

fvasco opened this issue Jul 26, 2017 · 3 comments

Comments

@fvasco
Copy link
Contributor

fvasco commented Jul 26, 2017

The current Mutex implementation is always fair or not?
Documentation should explicit it.

If current implementation isn't fair then is it possible to add an optional parameter to define a fairness policy?
@elizarov
Copy link
Contributor

It is fair.

fvasco pushed a commit to fvasco/kotlinx.coroutines that referenced this issue Jul 31, 2017
Mutex fairness documentation (Kotlin#90)
630b272
@fvasco fvasco closed this as completed Jul 31, 2017
fvasco pushed a commit to fvasco/kotlinx.coroutines that referenced this issue Aug 1, 2017
@fvasco
Mutex fairness documentation (Kotlin#90)
1fad557
elizarov pushed a commit that referenced this issue Aug 3, 2017
@elizarov
Mutex fairness documentation (#90)
f1a24b1
@elizarov
Copy link
Contributor

Released in version 0.18

@TYZRPVX
Copy link

TYZRPVX commented Jun 20, 2022

lock & unlock function make use of LockFreeLinkedListNode to ensure FIFO order

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@elizarov @TYZRPVX @fvasco