furrr 0.3.0
Breaking changes
-
future_options()
is now defunct and will be removed in the next minor
release of furrr. Please usefurrr_options()
instead (#137). -
The
lazy
argument offurrr_options()
has been completely removed. This
argument had no effect, as futures are always resolved before the
corresponding furrr function returns (#222).
Features / Fixes
-
future_walk()
and the other walk functions now avoid sending the results
of calling.f
back to the main process (#205). -
The
conditions
argument offurrr_options()
now supports selectively
ignoring conditions through anexclude
attribute. See?furrr_options
for
more information (#181). -
Standard output is now dropped from future results before they are returned
to the main process (#216). -
Condition objects are now dropped from future results before they are returned
to the main process (#216). -
Unskipped a test now that the upstream bug in future is fixed
(#218, futureverse/future.apply#10). -
Removed ellipsis in favor of the equivalent functions in rlang (#219).
-
Removed a multisession test related to whether or not an attempt was made to
load furrr on the workers (#217). -
Updated snapshot tests related to how testthat prints condition details
(#213).
Version requirements
-
furrr now requires R >=3.4.0, which is in line with the tidyverse.
-
lifecycle >=1.0.1, rlang >=1.0.2, purrr >=0.3.4, vctrs >=0.4.1,
globals >=0.14.0, and future >=1.25.0 are now required (#214).