furrr 0.4.0

Breaking changes

• All deprecated future_invoke_map_*() variants have been removed.

• All *_raw() variants from purrr have been removed, such as
  future_map_raw(). purrr 1.0.0 has deprecated these, they have limited use,
  and as far as we can tell no packages were using them (#298).

• future_options() has been removed. It has been defunct since furrr 0.3.0
  (May 2022).

Features / Fixes

• New future_map_vec(), future_map2_vec(), future_pmap_vec(), and
  future_imap_vec() to align with purrr (#261).

• When a furrr function errors, purrr's error index is no longer confusingly
  reported (#250).

• furrr_options() no longer drops the "ordering" attribute when casting
  non-integer chunk_size or scheduling to integer (#289, #290).

• furrr now looks up the purrr mapping function on the worker itself, rather
  than sending over its own copy of the function. This avoids possible issues
  when you have, say, purrr 1.0.0 locally but purrr 0.3.5 on the worker, where
  the internals of the purrr function may have changed between the two versions
  (#253).

• Fixed a rare issue where the deprecated .progress bar may cause an integer
  overflow with extremely long inputs (#288).

• Detangled furrr's documentation from purrr's to avoid some documentation
  inheritance issues (#286).

• Fixed an issue where generating random seeds could sporadically fail (#271,
  @HenrikBengtsson).

• Updated documentation examples and vignettes to use the base R pipe
  (#285, @HenrikBengtsson).

Version requirements

• furrr now requires R >=4.1.0, which is in line with the tidyverse (#285).

• lifecycle >=1.0.5, rlang >=1.1.7, purrr >=1.2.1, vctrs >=0.7.0,
  globals >=0.19.1, and future >=1.70.0 are now required.