Now ‘mirai’ futures can be canceled using cancel(),
which also interrupts them by default, which in turn frees up compute
resources sooner. Map-reduce API such as future.apply,
doFuture, and furrr can take advantage
of this by canceling all non-resolved futures whenever they detect an
error in one of the futures. Also, canceled futures can be
reset() and thereafter relaunched, possibly on another
future backend.
Now ‘mirai_multisession’ futures relay
immediateCondition:s in near real-time,
e.g. progression conditions signals by the
progressr package.
mirai::daemons() argument resilience is
being removed.nbrOfWorkers() and nbrOfFreeWorkers() did
not handle mirai dispatcher errors. Because those are integers, these
functions would return the error integer value instead of giving a
FutureError.