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
Copy file name to clipboardExpand all lines: NEWS.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,6 +19,7 @@
19
19
*`everywhere()` now returns a list of mirai, which may be waited for and inspected (thanks @dgkf#164).
20
20
*`everywhere()` drops argument '.serial' as serialization configurations are now registered via an argument at `daemons()`.
21
21
*`launch_local()` and `launch_remote()` simplified to take the argument 'n' instead of 'url' for how many daemons to launch.
22
+
*`launch_local()` and `launch_remote()` now launch daemons with the originally-supplied arguments by default.
22
23
*`launch_local()` now returns the number of daemons launched rather than invisible NULL.
23
24
*`ssh_config()` simplified to take the argument 'port' instead of 'host'. For SSH tunnelling, this is the port that will be used, and the hostname is now required to be '127.0.0.1' (no longer accepting 'localhost').
24
25
*`daemon()` gains the new argument 'dispatcher', which should be set to `TRUE` when connecting to dispatcher and `FALSE` when connecting directly to host.
As a mirai represents an async operation, it is never necessary to wait for it. Other code can continue to be run. Once it completes, the return value automatically becomes available at `$data`.
For easy programmatic use of `mirai()`, '.expr' accepts a pre-constructed language object, and also a list of named arguments passed via '.args'. So, the following would be equivalent to the above:
This implementation sends tasks immediately, and ensures that tasks are evenly-distributed amongst daemons. This means that optimal scheduling is not guaranteed as the duration of tasks cannot be known *a priori*. As an example, tasks could be queued at a daemon behind a long-running task, whilst other daemons are idle having already completed their tasks.
243
243
@@ -265,11 +265,11 @@ m <- mirai(capture.output(str(con)))
265
265
m[]
266
266
#> [1] "Formal class 'SQLiteConnection' [package \"RSQLite\"] with 8 slots"
Use `...` to further specify objects referenced but not defined in `.f` - the 'do' in the anonymous function below:
736
736
@@ -742,16 +742,16 @@ ml <- mirai_map(
742
742
)
743
743
#> Warning: mirai is launching one local daemon for a map operation as none previously set
744
744
ml
745
-
#> < mirai map [2/3] >
745
+
#> < mirai map [3/3] >
746
746
ml[]
747
747
#> $a
748
-
#> [1] "24"
748
+
#> [1] "1e"
749
749
#>
750
750
#> $b
751
-
#> [1] ea 6c
751
+
#> [1] af f5
752
752
#>
753
753
#> $c
754
-
#> [1] "0d0643"
754
+
#> [1] "786cf0"
755
755
```
756
756
Use of `mirai_map()` assumes that `daemons()` have previously been set. If not then one (non-dispatcher) daemon is set to allow the function to proceed. This ensures safe behaviour, but is unlikely to be optimal, so please ensure daemons are set beforehand.
0 commit comments