Skip to content

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 within future_promise (Thank you, @HenrikBengtsson! #123)

promises 1.3.2

CRAN release: 2024-11-27

  • Fixed bug introduced in 1.3.1, where promise domains that are active at promise resolution time stay active during handler callback, even if they weren’t active when the handler was registered. This was causing stack overflow for long promise chains with many active promise domains. (#115)

promises 1.3.1

CRAN release: 2024-11-26

  • Fixed bug where promise domains were forgotten when handlers were registered from within other handlers. (#110)

promises 1.3.0

CRAN release: 2024-04-05

  • is.promising is now an S3 method. (#104)

promises 1.2.1

CRAN release: 2023-08-10

promises 1.2.0.1

CRAN release: 2021-02-11

promises 1.1.1

CRAN release: 2020-06-09

promises 1.1.0

CRAN release: 2019-10-04

  • Fixed #49: promise_all() previously did not handle NULL values correctly. (#50))

  • new_promise_domain now takes a wrapOnFinally argument, which can be used to intercept registration of finally(). Previous versions treated finally as passing the same callback to then(onFulfilled=..., onRejected=...), and ignoring the result; for backward compatibility, promise domains will still treat finally that way by default (i.e. if wrapOnFinally is NULL, then finally will result in wrapOnFulfilled and wrapOnRejected being called, but if wrapOnFinally is provided then only wrapOnFinally will be called). (#43)

promises 1.0.1

CRAN release: 2018-04-13

  • Initial CRAN release