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.
Provides a header only, 'C++' interface to 'R' with enhancements over 'cpp11'. Enforces copy-on-write semantics consistent with 'R' behavior. Offers native support for ALTREP objects, 'UTF-8' string handling, modern 'C++11' features and idioms, and reduced memory requirements. Allows for vendoring, making it useful for restricted environments. Compared to 'cpp11', it adds support for converting 'C++' maps to 'R' lists, 'Roxygen' documentation directly in 'C++' code, proper handling of matrix attributes, support for nullable external pointers, bidirectional copy of complex number types, flexibility in type conversions, use of nullable pointers, and various performance optimizations.
Version: | 0.3.0 |
Depends: | R (≥ 4.0.0) |
Imports: | brio, cli, decor, desc, glue, tibble, tools, utils, vctrs, withr |
Suggests: | mockery, roxygen2, testthat (≥ 3.2.0) |
Published: | 2025-10-16 |
DOI: | 10.32614/CRAN.package.cpp4r |
Author: | Mauricio Vargas Sepulveda
|
Maintainer: | Mauricio Vargas Sepulveda <m.vargas.sepulveda at gmail.com> |
BugReports: | https://github.com/pachadotdev/cpp4r/issues |
License: | Apache License (≥ 2) |
URL: | https://cpp4r.org, https://github.com/pachadotdev/cpp4r |
NeedsCompilation: | no |
Materials: | README, NEWS |
CRAN checks: | cpp4r results |
Reference manual: | cpp4r.html , cpp4r.pdf |
Package source: | cpp4r_0.3.0.tar.gz |
Windows binaries: | r-devel: cpp4r_0.3.0.zip, r-release: cpp4r_0.3.0.zip, r-oldrel: cpp4r_0.3.0.zip |
macOS binaries: | r-release (arm64): cpp4r_0.3.0.tgz, r-oldrel (arm64): cpp4r_0.3.0.tgz, r-release (x86_64): cpp4r_0.3.0.tgz, r-oldrel (x86_64): cpp4r_0.3.0.tgz |
Please use the canonical form https://CRAN.R-project.org/package=cpp4r 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.