promises 1.3.3
-
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 withinfuture_promise(Thank you, @HenrikBengtsson! #123)
Full Changelog: v1.3.2...v1.3.3