commit | ecbc85cbdad134d868698e22c0fdd7220eaced0f | [log] [tgz] |
---|---|---|
author | Roman Elizarov <elizarov@gmail.com> | Fri Sep 14 12:52:50 2018 +0300 |
committer | Roman Elizarov <elizarov@gmail.com> | Sun Sep 23 19:11:23 2018 +0300 |
tree | d64f7e07053c845bfd9cc000ee8b2636e707177d | |
parent | 99c28aab64150e3f21df49a3a538b0ec93c7d2aa [diff] |
Fix exception aggregation to ensure atomic handling of exceptions * Removed legacy onFinishing handler support from JobSupport. - It is no longer needed, because handleJobException covers #208 * Fixed bugs that were masked by cancelling parent from onFinishing. * Consistent "Finishing" state was introduced in internal machinery: - Job enters finishing state when it is failing or it is completing and has children - Finishing state cleanly aggregates all failures, tracks cancellation and completion status * Job.isFailed is introduced as a consistent way to query the "failing" state of the job that was previously only implicitly available via invokeOnCompletion handler (cause != null means a failed job) and the documentation for both Job & Deferred is updated to reflect that. * Source-incompatible change: Job.invokeOnCompletion boolean parameter is change to onFailing. Such handlers are now invoked as soon as the job starts failing and the root cause exception of the failure is consistently passed to all the handlers. * The following internal methods were introduced to facilitate this: - Job.failParent(exception) is used by child to signal failure to parent - Job.cancelChild(parentJob) is used by parent to cancel child. * Child never aggregates exception received from it parent, but uses it as it root cause if there is no other exception. * JobSupport.handleJobException() logic for launch/actor is split into: - failParent - can be invoked multiple times on race; - handleJobException which is invoked exactly once. * Exception materiazization is much lazier now, which should significantly improve performance when cancelling large hierarchies. * Other minor perf improvements in JobSupport code. Fixes #585
Library support for Kotlin coroutines with multiplatform support. This is a companion version for Kotlin 1.2.70 release.
GlobalScope.launch { delay(1000) println("Hello from Kotlin Coroutines!") }
launch
and async
coroutine builders;Job
and Deferred
light-weight future with cancellation support;delay
and yield
top-level suspending functions;Channel
and Mutex
communication and synchronization primitives;produce
and actor
coroutine builders;select
expression support and more.Dispatchers.IO
dispatcher for blocking coroutines.Promise
support.runBlocking
single-threaded event loop.CompletableFuture
, Guava ListenableFuture
, and synchronous networking/IO.Note that these libraries are experimental and are subject to change.
The libraries are published to kotlinx bintray repository, linked to JCenter and pushed to Maven Central.
Add dependencies (you can also add other modules that you need):
<dependency> <groupId>org.jetbrains.kotlinx</groupId> <artifactId>kotlinx-coroutines-core</artifactId> <version>0.26.1</version> </dependency>
And make sure that you use the latest Kotlin version:
<properties> <kotlin.version>1.2.70</kotlin.version> </properties>
Add dependencies (you can also add other modules that you need):
implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-core:0.26.1'
And make sure that you use the latest Kotlin version:
buildscript { ext.kotlin_version = '1.2.70' }
Make sure that you have either jcenter()
or mavenCentral()
in the list of repositories:
repository { jcenter() }
Core modules of kotlinx.coroutines
are also available for Kotlin/JS and Kotlin/Native. If you write a common code that should get compiled or different platforms, add org.jetbrains.kotlinx:kotlinx-coroutines-core-common:<version>
to your common code dependencies.
Add kotlinx-coroutines-android
module as dependency when using kotlinx.coroutines
on Android:
implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-android:0.26.1'
This gives you access to Android Dispatchers.Main coroutine dispatcher and also makes sure that in case of crashed coroutine with unhandled exception this exception is logged before crashing Android application, similarly to the way uncaught exceptions in threads are handled by Android runtime.
In obfuscated code, fields with different types can have the same names, and AtomicReferenceFieldUpdater
may be unable to find the correct ones. To avoid field overloading by type during obfuscation, add this to your config:
-keepclassmembernames class kotlinx.** { volatile <fields>; }
This library is built with Gradle. To build it, use ./gradlew build
. You can import this project into IDEA, but you have to delegate build actions to Gradle (in Preferences -> Build, Execution, Deployment -> Build Tools -> Gradle -> Runner)
JAVA_HOME
environment variable.JDK_16
environment variable.All development (both new features and bug fixes) is performed in develop
branch. This way master
sources always contain sources of the most recently released version. Please send PRs with bug fixes to develop
branch. Fixes to documentation in markdown files are an exception to this rule. They are updated directly in master
.
The develop
branch is pushed to master
during release.