NEWS.md
call_mirai()
again (regression in 0.7.0), now returning a ‘miraiInterrupt’.is_mirai_interrupt()
to test if an object is a ‘miraiInterrupt’.daemons()
now takes ‘n’ and ‘.url’ arguments. ‘.url’ is an optional client URL allowing mirai tasks to be distributed across the network. Compatibility with existing interface is retained.server()
is exported for creating daemon / ephemeral processes on network resources.daemons()
and %>>%
deferred evaluation pipe.mirai()
gains a ‘.args’ argument for passing a list of objects already in the calling environment, allowing for example mirai(func(x, y, z), .args = list(x, y, z))
rather than having to specify mirai(func(x, y, z), x = x, y = y, z = z)
.is_mirai_error()
should be used in place of is_nul_byte()
, which is no longer re-exported.is_error_value()
can be used to test for all errors, including timeouts where the ‘.timeout’ argument has been used.%>>%
deferred evaluation pipe.mirai()
to ensure a mirai always resolves even if the child process crashes etc.is_mirai()
to test if an object is a mirai.$data
to optimally align with the underlying implementation.mirai()
added as an alias for eval_mirai()
; supports evaluating arbitrary length expressions wrapped in {}
.call_mirai()
. Access the $value
directly and an ‘unresolved’ logical NA will be returned if the async operation is yet to complete.stop_mirai()
added as a function to stop evaluation of an ongoing async operation.is_nul_byte()
and unresolved()
re-exported from {nanonext} to test for evaluation errors and resolution of a ‘mirai’ respectively.daemons()
interface to set and manage persistent background processes for receiving ‘mirai’ requests.