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
Currently, if a Task needs to be executed after a task, sequentially, then andThen(Task<R> task) needs to be used.
This introduces a few issues where if code is like andThen(someTaskReturningFunction()) then someTaskReturningFunction() will get executed though the Task returned by it may not be run.
Should a andThen(Function1 func) be supported to allow sequential execution of a task after a parent task by also ensuring the task supplying argument is not invoked.
This will be close to withSideEffect but sometimes, andThen is more suited for the use case.
The text was updated successfully, but these errors were encountered:
Hi,
Currently, if a
Task
needs to be executed after a task, sequentially, thenandThen(Task<R> task)
needs to be used.This introduces a few issues where if code is like
andThen(someTaskReturningFunction())
thensomeTaskReturningFunction()
will get executed though theTask
returned by it may not be run.Should a
andThen(Function1 func)
be supported to allow sequential execution of a task after a parent task by also ensuring the task supplying argument is not invoked.This will be close to
withSideEffect
but sometimes,andThen
is more suited for the use case.The text was updated successfully, but these errors were encountered: