Implementations of apply(), by(), eapply(), lapply(), Map(), mapply(), replicate(), sapply(), tapply(), and vapply() that can be resolved using any future-supported backend, e.g. parallel on the local machine or distributed on a compute cluster. These future_*apply() functions come with the same pros and cons as the corresponding base-R *apply() functions but with the additional feature of being able to be processed via the future framework.
Version: 1.2.0 [2019-03-06]
Attributes 'add' and 'ignore' of argument 'future.globals' were ignored although support for them was added in future (>= 1.10.0).
Validation of L'Ecuyer-CMRG RNG seeds failed in recent R devel.
Version: 1.1.0 [2019-01-16]
Elements can be processed in random order by setting attribute 'ordering' to "random" of argument 'future.chunk.size' or 'future.scheduling', e.g. future.chunk.size = structure(TRUE, ordering = "random"). This can help improve load balancing in cases where there is a correlation between processing time and ordering of the elements. Note that the order of the returned values is not affected when randomizing the processing order.
Swapped order of arguments 'future.lazy' and 'future.seed' to be consistent with ditto arguments of future::future().
Version: 1.0.1 [2018-08-26]
DOCUMENTATION / LICENCE:
For list objects 'X' where X != as.list(X), future_lapply(X) did not give the same result as lapply(X). Analogously for future_vapply(X).
future_mapply() could drop class attribute on elements iterated over,
because .subset() was used internally instead of
[(). For instance,
iteration over Date objects were affected.
Version: 1.0.0 [2018-06-19]
Added future_apply(), future_mapply(), and future_Map().
future.chunk.size as an alternative to argument
future.scheduling for controlling the average number of elements
processed per future ("chunk"). In R 3.5.0, the parallel package
introduced argument 'chunk.size'.
The maximum total size of globals allowed (option 'future.globals.maxSize') per future ("chunk") is now scaled up by the number of elements processed by the future ("chunk") making the protection approximately invariant to the amount of chunking (arguments 'future.scheduling' and 'future.chunk.size').
future_lapply(X, ...) did not search for globals in 'X'.
future_vapply() did not return the same dimension names as vapply() when FUN.VALUE had no names but FUN(X[]) had.
Version: 0.2.0 [2018-05-01]
Version: 0.1.0 [2018-01-15]
Version: 0.0.3 [2017-12-06]
Version: 0.0.2 [2017-12-06]
Version: 0.0.0-9000 [2017-08-31]
Added future_lapply() - originally from the future package.