Up to [cvs.NetBSD.org] / pkgsrc / sysutils / R-later
Request diff between arbitrary revisions
Keyword substitution: kv
Default branch: MAIN
R*: remove execinfo workarounds Not needed with R-Rcpp 1.1.2, and some of these broke e.g. macOS
(sysutils/R-later) Fix build on Darwin,Linux, hopefully
(sysutils/R-later) Updated 1.4.1 to 1.4.8 (pkgsrc) - Add patch to resolve undefined function backtrace_symbols (in /usr/lib/libexecinfo) (upstream) # later 1.4.8 * Fixed #262: Internal update for compatibility with Rcpp re. `Rf_error` handling (#263). # later 1.4.7 * Fixed #256: compilation failure with glibc >= 2.43 and GCC >= 15, caused by the C11 `once_flag` type now being defined in `<stdlib.h>` under C23. Renamed internal tinycthread symbols to avoid the namespace collision (#257). # later 1.4.6 * Improved responsiveness when idle at the R console on POSIX systems (#251). * Fixes #249: Moved the contents of `inst/include/later.h` into `later_api.h` to ensure R headers are not included before Rcpp headers when Rcpp auto-includes `$PACKAGE.h` in RcppExports.cpp. The public API header remains `later_api.h` (#250). # later 1.4.5 * Now requires R >= 3.5.0 (for `R_UnwindProtect()`) and Rcpp >= 1.0.10. Removed legacy non-unwind-protect code paths that were previously used as a fallback on older R versions (#241). # later 1.4.4 * Fixed timings in a test (#237). No user-facing changes. # later 1.4.3 * 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 * Fixed #208: Fixed `keyword is hidden by macro definition` compiler warning when using a C23 compiler. (@shikokuchuo, #209)
*: recursive bump for boost 1.89
R-later: require libatomic on i386 atomic64.mk is already included but doesn't provide the library by default on i386.
(sysutils/R-later) Updated 1.3.2 to 1.4.1 # later 1.4.1 * 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 * 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)
(sysutils/R-later) Updated 1.3.0 to 1.3.2 # later 1.3.2 * 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 * For C function declarations that take no parameters, added `void` parameter. (#172)
sysutils/R-later: convert to using mk/atomic64.mk.
(sysutils/R-later) Updated 1.2.0 to 1.3.0 # 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)
(sysutils/R-later) Updated 1.0.0 to 1.2.0 ## 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)
(sysutils/R-later) Updated to 1.0.0 ## 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))
R-later: add missing dependency R-BH. Fixes build. From Benjamin Lorenz in PR pkg/54517
R-later: initial commit Executes arbitrary R or C functions some time after the current time, after the R execution stack has emptied.