later 0.7.4

• Fixed issue #45 and #63: glibc 2.28 and musl (used on Arch and Alpine Linux) added support for C11-style threads.h, which masked functions from the tinycthread library used by later. Later now detects support for threads.h and uses it if available; otherwise it uses tinycthread. PR #64

later 0.7.3

• Fixed issue #57: If a user interrupt occurred when later (internally) called sys.nframe(), the R process would crash. PR #58

later 0.7.2

• Fixed issue #48: Occasional timedwait errors from later::run_now. Thanks, @vnijs! PR #49

• Fixed a build warning on OS X 10.11 and earlier. PR #54

later 0.7.1

• Fixed issue #39: Calling the C++ function later::later() from a different thread could cause an R GC event to occur on that thread, leading to memory corruption. PR #40

• Decrease latency of repeated top-level execution.

later 0.6

• Fix a hang on address sanitized (ASAN) builds of R. Issue #16, PR #17

• The run_now() function now takes a timeoutSecs argument. If no tasks are ready to run at the time run_now(timeoutSecs) is invoked, we will wait up to timeoutSecs for one to become ready. The default value of 0 means run_now() will return immediately if no tasks are ready, which is the same behavior as in previous releases. PR #19

• The run_now() function used to return only when it was unable to find any more tasks that were due. This means that if tasks were being scheduled at an interval faster than the tasks are executed, run_now() would never return. This release changes that behavior so that a timestamp is taken as run_now() begins executing, and only tasks whose timestamps are earlier or equal to it are run. PR #18

• Fix compilation errors on Solaris. Reported by Brian Ripley. PR #20