You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have use-cases when we need an explicit Job object with children. However, the regular Job() constructor produces a job that cannot complete normally. You can only cancel() it, thus also cancelling all its children. Right now CompletableDeferred<Unit>() is used as such a primitive. It works final, but just looks quite unnatural, so the proposal is to add a dedicated CompletableJob() primitive that has a complete() method to complete its normally.
The text was updated successfully, but these errors were encountered:
We have use-cases when we need an explicit
Job
object with children. However, the regularJob()
constructor produces a job that cannot complete normally. You can onlycancel()
it, thus also cancelling all its children. Right nowCompletableDeferred<Unit>()
is used as such a primitive. It works final, but just looks quite unnatural, so the proposal is to add a dedicatedCompletableJob()
primitive that has acomplete()
method to complete its normally.The text was updated successfully, but these errors were encountered: