Skip to content

Conversation

@qwwdfsad
Copy link
Member

No description provided.

@qwwdfsad qwwdfsad force-pushed the mutex-on-lock branch 2 times, most recently from a66ef09 to 948c7e3 Compare July 30, 2021 14:55
@qwwdfsad qwwdfsad changed the title [DRAFT] Preparation to Mutex.onLock deprecation Mutex.onLock deprecation Sep 30, 2021
Copy link
Collaborator

@dkhalanskyjb dkhalanskyjb left a comment

Choose a reason for hiding this comment

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

There was one more mention of onLock, but I pushed a commit to remove it.

@qwwdfsad qwwdfsad merged commit 7755edb into develop Oct 20, 2021
@qwwdfsad qwwdfsad deleted the mutex-on-lock branch October 20, 2021 08:40
yorickhenning pushed a commit to yorickhenning/kotlinx.coroutines that referenced this pull request Jan 28, 2022
* Actually test 'onLock' and the corresponding concurrency and cancellation of Reactive's onSend
* Update benchmarks
* Non-linearizable implementation of PublisherCoroutine.onSend that isn't using Mutex.onLock
* Deprecate Mutex.onLock

Fixes Kotlin#2794

Co-authored-by: Dmitry Khalanskiy <Dmitry.Khalanskiy@jetbrains.com>
pablobaxter pushed a commit to pablobaxter/kotlinx.coroutines that referenced this pull request Sep 14, 2022
* Actually test 'onLock' and the corresponding concurrency and cancellation of Reactive's onSend
* Update benchmarks
* Non-linearizable implementation of PublisherCoroutine.onSend that isn't using Mutex.onLock
* Deprecate Mutex.onLock

Fixes Kotlin#2794

Co-authored-by: Dmitry Khalanskiy <Dmitry.Khalanskiy@jetbrains.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants