{"Package":"later","Type":"Package","Title":"Utilities for Scheduling Functions to Execute Later with Event\nLoops","Version":"1.4.1","Authors@R":"c(\nperson(\"Winston\", \"Chang\", role = c(\"aut\", \"cre\"), email = \"winston@posit.co\"),\nperson(\"Joe\", \"Cheng\", role = c(\"aut\"), email = \"joe@posit.co\"),\nperson(\"Charlie\", \"Gao\", role = c(\"aut\"), email = \"charlie.gao@shikokuchuo.net\", comment = c(ORCID = \"0000-0002-0750-061X\")),\nperson(family = \"Posit Software, PBC\", role = \"cph\"),\nperson(\"Marcus\", \"Geelnard\", role = c(\"ctb\", \"cph\"), comment = \"TinyCThread library, https://tinycthread.github.io/\"),\nperson(\"Evan\", \"Nemerson\", role = c(\"ctb\", \"cph\"), comment = \"TinyCThread library, https://tinycthread.github.io/\")\n)","Description":"Executes arbitrary R or C functions some time after the current\ntime, after the R execution stack has emptied. The functions are scheduled\nin an event loop.","URL":"https://r-lib.github.io/later/, https://github.com/r-lib/later","BugReports":"https://github.com/r-lib/later/issues","License":"MIT + file LICENSE","Imports":"Rcpp (>= 0.12.9), rlang","LinkingTo":"Rcpp","RoxygenNote":"7.3.2","Suggests":"knitr, nanonext, R6, rmarkdown, testthat (>= 2.1.0)","VignetteBuilder":"knitr","Encoding":"UTF-8","NeedsCompilation":"yes","Packaged":"2024-11-27 22:51:17 UTC; jcheng","Author":"Winston Chang [aut, cre],\nJoe Cheng [aut],\nCharlie Gao [aut] (),\nPosit Software, PBC [cph],\nMarcus Geelnard [ctb, cph] (TinyCThread library,\nhttps://tinycthread.github.io/),\nEvan Nemerson [ctb, cph] (TinyCThread library,\nhttps://tinycthread.github.io/)","Maintainer":"Winston Chang ","Repository":"CRAN","Date/Publication":"2024-11-27 23:40:02 UTC","repoType":"cran","tarballUrl":"ftp://cran.r-project.org/pub/R/src/contrib/later_1.4.1.tar.gz","jsonAuthors":[{"name":"Winston Chang","email":"winston@posit.co","maintainer":true},{"name":"Joe Cheng","email":"joe@posit.co","maintainer":false},{"name":"Charlie Gao","email":"charlie.gao@shikokuchuo.net","maintainer":false},{"name":" Posit Software, PBC","email":null,"maintainer":false},{"name":"Marcus Geelnard","email":null,"maintainer":false},{"name":"Evan Nemerson","email":null,"maintainer":false}],"readme":"# later\n\n\n[![R build status](https://github.com/r-lib/later/actions/workflows/R-CMD-check.yaml/badge.svg)](https://github.com/r-lib/later/actions)\n\n\n\nSchedule an R function or formula to run after a specified period of time. Similar to JavaScript's `setTimeout` function. Like JavaScript, R is single-threaded so there's no guarantee that the operation will run exactly at the requested time, only that at least that much time will elapse.\n\nTo avoid bugs due to reentrancy, by default, scheduled operations only run when there is no other R code present on the execution stack; i.e., when R is sitting at the top-level prompt. You can force past-due operations to run at a time of your choosing by calling `later::run_now()`.\n\nThe mechanism used by this package is inspired by Simon Urbanek's [background](https://github.com/s-u/background) package and similar code in Rhttpd.\n\n## Installation\n\n```r\nremotes::install_github(\"r-lib/later\")\n```\n\n## Usage from R\n\nPass a function (in this case, delayed by 5 seconds):\n\n```r\nlater::later(function() {\n print(\"Got here!\")\n}, 5)\n```\n\nOr a formula (in this case, run as soon as control returns to the top-level):\n\n```r\nlater::later(~print(\"Got here!\"))\n```\n### File Descriptor Readiness\n\nIt is also possible to have a function run based on when file descriptors are ready for reading or writing, at some indeterminate time in the future.\n\nBelow, a logical vector is printed indicating which of file descriptors 21 or 22 were ready, subject to a timeout of 1s. Instead of just printing the result, the supplied function can also do something more useful such as reading from the descriptor.\n\n```r\nlater::later_fd(print, c(21L, 22L), timeout = 1)\n```\n\nThis is useful in particular for asynchronous or streaming data transfer over the network / internet, so that reads can be made from TCP sockets as soon as data is available. `later::later_fd()` pairs well with functions such as `curl::multi_fdset()` that return the relevant file descriptors to be monitored .\n\n## Usage from C++\n\nYou can also call `later::later` from C++ code in your own packages, to cause your own C-style functions to be called back. This is safe to call from either the main R thread or a different thread; in both cases, your callback will be invoked from the main R thread.\n\n`later::later` is accessible from `later_api.h` and its prototype looks like this:\n\n```cpp\nvoid later(void (*func)(void*), void* data, double secs)\n```\n\nThe first argument is a pointer to a function that takes one `void*` argument and returns void. The second argument is a `void*` that will be passed to the function when it's called back. And the third argument is the number of seconds to wait (at a minimum) before invoking.\n\n`later::later_fd` is also accessible from `later_api.h` and its prototype looks like this:\n\n```cpp\nvoid later_fd(void (*func)(int *, void *), void *data, int num_fds, struct pollfd *fds, double secs)\n```\nThe first argument is a pointer to a function that takes two arguments: the first being an `int*` array provided by `later_fd()` when called back, and the second being a `void*`. The `int*` array will be the length of `num_fds` and contain the values `0`, `1` or `NA_INTEGER` to indicate the readiness of each file descriptor, or an error condition respectively. The second argument `data` is passed to the `void*` argument of the function when it's called back. The third is the total number of file descriptors being passed, the fourth a pointer to an array of `stuct pollfds`, and the fifth the number of seconds to wait until timing out.\n\nTo use the C++ interface, you'll need to add `later` to your `DESCRIPTION` file under both `LinkingTo` and `Imports`, and also make sure that your `NAMESPACE` file has an `import(later)` entry.\n\n### Background tasks\n\nFinally, this package also offers a higher-level C++ helper class to make it easier to execute tasks on a background thread. It is also available from `later_api.h` and its public/protected interface looks like this:\n\n```cpp\nclass BackgroundTask {\n\npublic:\n BackgroundTask();\n virtual ~BackgroundTask();\n\n // Start executing the task\n void begin();\n\nprotected:\n // The task to be executed on the background thread.\n // Neither the R runtime nor any R data structures may be\n // touched from the background thread; any values that need\n // to be passed into or out of the Execute method must be\n // included as fields on the Task subclass object.\n virtual void execute() = 0;\n\n // A short task that runs on the main R thread after the\n // background task has completed. It's safe to access the\n // R runtime and R data structures from here.\n virtual void complete() = 0;\n}\n```\n\nCreate your own subclass, implementing a custom constructor plus the `execute` and `complete` methods.\n\nIt's critical that the code in your `execute` method not mutate any R data structures, call any R code, or cause any R allocations, as it will execute in a background thread where such operations are unsafe. You can, however, perform such operations in the constructor (assuming you perform construction only from the main R thread) and `complete` method. Pass values between the constructor and methods using fields.\n\n```rcpp\n#include \n#include \n\nclass MyTask : public later::BackgroundTask {\npublic:\n MyTask(Rcpp::NumericVector vec) :\n inputVals(Rcpp::as >(vec)) {\n }\n\nprotected:\n void execute() {\n double sum = 0;\n for (std::vector::const_iterator it = inputVals.begin();\n it != inputVals.end();\n it++) {\n\n sum += *it;\n }\n result = sum / inputVals.size();\n }\n\n void complete() {\n Rprintf(\"Result is %f\\n\", result);\n }\n\nprivate:\n std::vector inputVals;\n double result;\n};\n```\n\nTo run the task, `new` up your subclass and call `begin()`, e.g. `(new MyTask(vec))->begin()`. There's no need to keep track of the pointer; the task object will delete itself when the task is complete.\n\n```r\n// [[Rcpp::export]]\nvoid asyncMean(Rcpp::NumericVector data) {\n (new MyTask(data))->begin();\n}\n```\n\nIt's not very useful to execute tasks on background threads if you can't get access to the results back in R. The [promises](https://github.com/rstudio/promises) package complements later by providing a \"promise\" abstraction.","jobInfo":{"package":"later","version":"1.4.1","parsingStatus":"success","parserVersion":2,"parsedAt":"2024-11-28T01:29:48+0000"}}

Description

Usage

Arguments