| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
All checksums have been double-checked against existing RMD160 and
SHA512 hashes
|
|
|
|
# later 1.3.0
* 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
* 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
* 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)
|
|
## later 1.0.0
* Added private event loops: these are event loops that can be run
independently from the global event loop. These are useful when you
have code that schedules callbacks with `later()`, and you want to
call `run_now()` block and wait for those callbacks to execute
before continuing. Without private event loops, if you call
`run_now()` to wait until a particular callback has finished, you
might inadvertantly run other callbacks that were scheduled by other
code. With private event loops, you can create a private loop,
schedule a callback on it, then call `run_now()` on that loop until
it executes, all without interfering with the global
loop. ([#84](https://github.com/r-lib/later/pull/84))
|
|
From Benjamin Lorenz in PR pkg/54517
|
|
Executes arbitrary R or C functions some time after the current time,
after the R execution stack has emptied.
|
