The Rcpp team is proud to announce release 1.0.6 of Rcpp which arrived at CRAN earlier today, and has been uploaded to Debian too. Windows and macOS builds should appear at CRAN in the next few days. This marks the first release on the new six-months cycle announced with release 1.0.5 in July. As reminder, interim ‘dev’ or ‘rc’ releases will often be available in the Rcpp drat repo; this cycle there were four.
Rcpp has become the most popular way of enhancing R with C or C++ code. As of today, 2174 packages on CRAN depend on Rcpp for making analytical code go faster and further (which is an 8.5% increase just since the last release), along with 207 in BioConductor.
This release features six different pull requests from five different contributors, mostly fixing fairly small corner cases, plus some minor polish on documentation and continuous integration. Before releasing we once again made numerous reverse dependency checks none of which revealed any issues. So the passage at CRAN was pretty quick despite the large dependency footprint, and we are once again grateful for all the work the CRAN maintainers do.
Changes in Rcpp patch release version 1.0.6 (2021-01-14)
Changes in Rcpp API:
Replace remaining few uses of
R_ExternalPtrAddr(Kevin in #1098 fixing #1097).
DataFrame(Walter Somerville in #1099 fixing #1094).
Remove a misleading-to-wrong comment (Mattias Ellert in #1109 cleaning up after #1049).
Address a sanitizer report by initializing two private
boolvariables (Benjamin Christoffersen in #1113).
External pointer finalizer toggle default values were corrected to true (Dirk in #1115).
Changes in Rcpp Documentation:
- Several URLs were updated to https and/or new addresses (Dirk).
Changes in Rcpp Deployment:
- Added GitHub Actions CI using the same container-based setup used previously, and also carried code coverage over (Dirk in #1128).
Changes in Rcpp support functions:
Rcpp.package.skeleton()avoids warning from R. (Dirk)
Thanks to my CRANberries, you can also look at a diff to the previous release. Questions, comments etc should go to the rcpp-devel mailing list off the R-Forge page. Bugs reports are welcome at the GitHub issue tracker as well (where one can also search among open or closed issues); questions are also welcome under
rcpp tag at StackOverflow which also allows searching among the (currently) 2616 previous questions.
If you like this or other open-source work I do, you can sponsor me at GitHub. My sincere thanks to my current sponsors for me keeping me caffeinated.
This post by Dirk Eddelbuettel originated on his Thinking inside the box blog. Please report excessive re-aggregation in third-party for-profit settings.