Skip to content

promises 1.3.3

Choose a tag to compare

@schloerke schloerke released this 24 Jun 13:08
f5f7953
  • Changed the way we create future objects to stay compatible with new versions of {future}. Apparently the way we were doing it was never idiomatic and only worked by accident. (#121)

  • Fixed #122: Use future::future(..., lazy = TRUE) to avoid manual capturing of state within future_promise (Thank you, @HenrikBengtsson! #123)

Full Changelog: v1.3.2...v1.3.3