-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Version 1.3.0 #1462
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
Merged
Merged
Version 1.3.0 #1462
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… with non-virtual time Fixes #1434
…ctor.FlowKt with properly named files Otherwise, it leads to a weird classname clash and forces to write FQ imports
* Introduce (again) flowProduce in order to properly propagate cancellation to the upstream in flatMapMerge. Previously this issue was masked by SerializingCollector fast-path * Re-implement flatMapMerge via the channel to have context preservation property Fixes #1440
* Optimize select expression registration phase There is no need for multi-word atomic performAtomicIfNotSelected operation when enqueuing select node for operation. We can simply enqueue (addLast) xxxSelect node (SendSelect, ReceiveSelect, LockSelect). If the coroutine that rendezvous with this node finds out that the select expression was already selected, then it'll try again. * Removed SelectInstance.performAtomicIfNotSelected function * Removed Mutex.TryEnqueueLockDesc class, simplified onLock * Removed AbstractSendChannel.TryEnqueueSendDesc class, simpler onSend * Removed AbstractChannel.TryEnqueueReceiveDesc class, simpler onReceive * Simplified SelectInstance.disposeOnSelect. It does not have to do atomic addLastIf operation. Can do a simple addLast. * Fixed unlimited channel select onSend on closed channel It was hanging not being able to properly see that the channel was already closed at that send attempt should fail.
* Flow guide by example * Consistent chapter naming and ordering in docs * Make "supervision" a subsection of "Exception Handling" chapter * Knit: filter out sampleStart/End from Knit-generated source files * Knit: Support example auto-numbering
# Conflicts: # ui/kotlinx-coroutines-android/animation-app/gradle.properties # ui/kotlinx-coroutines-android/example-app/gradle.properties
elizarov
suggested changes
Aug 23, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some grammar nits. Great otherwise.
29e743d
to
6348be1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.