The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.

coro: 'Coroutines' for R

Provides 'coroutines' for R, a family of functions that can be suspended and resumed later on. This includes 'async' functions (which await) and generators (which yield). 'Async' functions are based on the concurrency framework of the 'promises' package. Generators are based on a dependency free iteration protocol defined in 'coro' and are compatible with iterators from the 'reticulate' package.

Version: 1.1.0
Depends: R (≥ 3.5.0)
Imports: rlang (≥ 0.4.12)
Suggests: knitr, later (≥ 1.1.0), magrittr (≥ 2.0.0), promises, reticulate, rmarkdown, testthat (≥ 3.0.0)
Published: 2024-11-05
DOI: 10.32614/CRAN.package.coro
Author: Lionel Henry [aut, cre], Posit Software, PBC [cph, fnd]
Maintainer: Lionel Henry <lionel at posit.co>
BugReports: https://github.com/r-lib/coro/issues
License: MIT + file LICENSE
URL: https://github.com/r-lib/coro, https://coro.r-lib.org/
NeedsCompilation: no
Materials: README NEWS
CRAN checks: coro results

Documentation:

Reference manual: coro.pdf
Vignettes: Generators (source, R code)

Downloads:

Package source: coro_1.1.0.tar.gz
Windows binaries: r-devel: coro_1.1.0.zip, r-release: coro_1.1.0.zip, r-oldrel: coro_1.1.0.zip
macOS binaries: r-release (arm64): coro_1.1.0.tgz, r-oldrel (arm64): coro_1.1.0.tgz, r-release (x86_64): coro_1.1.0.tgz, r-oldrel (x86_64): coro_1.1.0.tgz
Old sources: coro archive

Reverse dependencies:

Reverse imports: brulee, cito, crumble, geodl, luz, scDHA, SCFA, selenider, tabnet, torch
Reverse suggests: familiar, openalexR, plumber, torchdatasets, torchvision

Linking:

Please use the canonical form https://CRAN.R-project.org/package=coro to link to this page.

These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.