coro: 'Coroutines' for R

Canonical link: https://rscholar.com/pkg/coro

Lionel Henry • Posit Software • View description and downloads View dependencies GitHub project

2020 Published

0 Citations

2 Authors

6 Revisions

1.1.0 Version

MIT License

Referenced by ⇅	Year
trampoline: Make Functions that Can Recurse Infinitely (Version 0.1.1)	2021
brulee: High-Level Modeling Functions with 'torch' (Version 0.3.0)	2021
cito: Building and Training Neural Networks (Version 1.1)	2022
crumble: Flexible and General Mediation Analysis Using Riesz Representers (Version 0.1.2)	2024
deepregression: Fitting Deep Distributional Regression (Version 2.2.0)	2021
ellmer: Chat with Large Language Models (Version 0.1.0)	2025
familiar: End-to-End Automated Machine Learning and Model Evaluation (Version 1.5.0)	2022
geodl: Geospatial Semantic Segmentation with Torch and Terra (Version 0.2.0)	2024
luz: Higher Level 'API' for 'torch' (Version 0.4.0)	2021
openalexR: Getting Bibliographic Records from 'OpenAlex' Database Using 'DSL' API (Version 1.4.0)	2022
plumber: An API Generator for R (Version 1.2.2)	2016
scDHA: Single-Cell Decomposition using Hierarchical Autoencoder (Version 1.2.2)	2021
selenider: Concise, Lazy and Reliable Wrapper for 'chromote' and 'selenium' (Version 0.4.0)	2023
shapr: Prediction Explanation with Dependence-Aware Shapley Values (Version 0.2.2)	2020
shiny: Web Application Framework for R (Version 1.10.0)	2012
shinychat: Chat UI Component for 'shiny' (Version 0.1.1)	2024
tabnet: Fit 'TabNet' Models for Classification and Regression (Version 0.6.0)	2021
torch: Tensors and Neural Networks with 'GPU' Acceleration (Version 0.13.0)	2020
torchdatasets: Ready to Use Extra Datasets for Torch (Version 0.3.1)	2021
torchvision: Models, Datasets and Transformations for Images (Version 0.6.0)	2020

RPKG Scholar presents a tabulation of an author's contribution in the development of R packages stored in the Comprehensive R Archive Network (CRAN). Within this site, we consider package dependencies (suggests,imports,depends,enhances) as citations because we believe that using one's package to develop another is tantamount to citing the author of the package being imported, suggested or enhanced.