Skip to content

Releases: r-lib/later

later 1.4.4

27 Aug 09:06
e0a848e
Compare
Choose a tag to compare
  • Fixed timings in a test (#237). No user-facing changes.

later 1.4.3

20 Aug 07:12
7d63f36
Compare
Choose a tag to compare
  • Fixed #215: The autorun argument of create_loop(), long deprecated, is removed (#222).

  • Fixed #167: .Random.seed is no longer affected when the package is loaded (#220).

  • Set file-level variables as static to avoid triggering -Wmissing-variable-declarations (@MichaelChirico, #163).

later 1.4.2

08 Apr 09:07
78933e3
Compare
Choose a tag to compare
  • Fixed #208: Fixed keyword is hidden by macro definition compiler warning when using a C23 compiler. (@shikokuchuo, #209)

later 1.4.1

28 Nov 02:48
Compare
Choose a tag to compare
  • Fixed #203: Resolves an issue where packages that have LinkingTo: later (including promises and httpuv) and were built against later 1.4.0, would fail to load on systems that actually had older versions of later installed, erroring out with the message "function 'execLaterFdNative' not provided by package 'later'". With this fix, such dependent packages should gracefully deal with older versions at load time, and complain with helpful error messages if newer C interfaces (than are available on the installed later) are accessed. (#204)

later 1.4.0

27 Nov 15:37
Compare
Choose a tag to compare
  • Adds later_fd() which executes a function when a file descriptor is ready for reading or writing, at some indeterminate time in the future (subject to an optional timeout). This facilitates an event-driven approach to asynchronous or streaming downloads. (@shikokuchuo and @jcheng5, #190)

  • Fixed #186: Improvements to package load time as rlang is now only loaded when used. This is a notable efficiency for packages with only a 'linking to' dependency on later. Also updates to native symbol registration from dynamic lookup. (@shikokuchuo and @wch, #187)

  • Fixed #191: Errors raised in later callbacks were being re-thrown as generic C++ std::runtime_error with Rcpp >= 1.0.10 (since 2022!). (@shikokuchuo and @lionel-, #192)

later 1.3.2

06 Dec 21:36
0668a28
Compare
Choose a tag to compare
  • Fixed unused variable compiler warning. (@MichaelChirico, #176)

  • Fixed #177: The order of includes in later.h could cause compilation errors on some platforms. (@jeroen, #178)

  • Closed #181: Fix R CMD check warning re error() format strings (for r-devel). (#133)

later 1.3.1

02 May 18:16
@wch wch
Compare
Choose a tag to compare
  • For C function declarations that take no parameters, added void parameter. (#172)

later 1.3.0

18 Aug 16:42
ed0c1cb
Compare
Choose a tag to compare
  • Closed #148: When later was attached, parallel::makeForkCluster() would fail. (#149)

  • Fixed #150: It was possible for callbacks to execute in the wrong order if the clock time was changed in between the scheduling of two callbacks. (#151)

later 1.2.0

23 Apr 15:24
@wch wch
Compare
Choose a tag to compare
  • Closed #138: later is now licensed as MIT. (#139)

  • Closed #140: Previously, the event loop stopped running if the R process was forked. (#141)

  • Closed #143: Packages which link to later no longer need to take a direct dependency on Rcpp, because later.h no longer includes Rcpp.h. (#144)

  • Removed dependency on the BH package. C++11 is now required. (#147)

later 1.1.0.1

05 Jun 17:50
@wch wch
Compare
Choose a tag to compare
  • Private event loops are now automatically run by their parent. That is, whenever an event loop is run, its children event loops are automatically run. The create_loop() function has a new parameter parent, which defaults to the current loop. The auto-running behavior can be disabled by using create_loop(parent=NULL). (#119)

  • Fixed #73, #109: Previously, later did not build on some platforms, notably ARM, because the -latomic linker was needed on those platforms. A configure script now detects when -latomic is needed. (#114)

  • Previously, execLaterNative was initialized when the package was loaded, but not execLaterNative2, resulting in a warning message in some cases. (#116)