Rcpp

R: News for Package 'Rcpp' const macros = { "\\R": "\\textsf{R}", "\\mbox": "\\text", "\\code": "\\texttt"}; function processMathHTML() { var l = document.getElementsByClassName('reqn'); for (let e of l) { katex.render(e.textContent, e, { throwOnError: false, macros }); } return; } NEWS R Documentation News for Package Rcpp Changes in Rcpp non-release version 1.1.1-1.1 (2026-04-19) Please see pr #1466 addressing #1465 for context (plus change from #1460 , and R_getRegisteredNamespace from #1469 ) This is an unplanned, unscheduled and uncalled for non-release made solely to unplug CRAN from late-breaking changes in R 4.6.0 Version 1.1.1-1.1 is identical to 1.1.1-1 apart from DESCRIPTION, ChangeLog and NEWS and exist solely to increment the version counter. Changes in Rcpp release version 1.1.1 (2026-01-08) Changes in Rcpp API: An unused old R function for a compiler version check has been removed after checking no known package uses it (Dirk in #1395 ) A narrowing warning is avoided via a cast (Dirk in #1398 ) Demangling checks have been simplified (Iñaki in #1401 addressing #1400 ) The treatment of signed zeros is now improved in the Sugar code (Iñaki in #1404 ) Preparations for phasing out use of Rf_error have been made (Iñaki in #1407 ) The long-deprecated function loadRcppModules() has been removed (Dirk in #1416 closing #1415 ) Some non-API includes from R were refactored to accommodate R-devel changes (Iñaki in #1418 addressing #1417 ) An accessor to Rf_rnbeta has been removed (Dirk in #1419 also addressing #1420 ) Code accessing non-API Rf_findVarInFrame now uses R_getVarEx (Dirk in #1423 fixing #1421 ) Code conditional on the R version now expects at least R 3.5.0; older code has been removed (Dirk in #1426 fixing #1425 ) The non-API ATTRIB entry point to the R API is no longer used (Dirk in #1430 addressing #1429 ) The unwind-protect mechanism is now used unconditionally (Dirk in #1437 closing #1436 ) Changes in Rcpp Attributes: The OpenMP plugin has been generalized for different macOS compiler installations (Kevin in #1414 ) Changes in Rcpp Documentation: Vignettes are now processed via a new "asis" processor adopted from R.rsp (Dirk in #1394 fixing #1393 ) R is now cited via its DOI (Dirk) A (very) stale help page has been removed (Dirk in #1428 fixing #1427 ) The main README.md was updated emphasizing r-universe in favor of the local drat repos (Dirk in #1431 ) Changes in Rcpp Deployment: A temporary change in R-devel concerning NA part in complex variables was accommodated, and then reverted (Dirk in #1399 fixing #1397 ) The macOS CI runners now use macos-14 (Dirk in #1405 ) A message is shown if R.h is included before Rcpp headers as this can lead to errors (Dirk in #1411 closing #1410 ) Old helper functions use message() to signal they are not used, deprecation and removal to follow (Dirk in #1413 closing #1412 ) Three tests were being silenced following #1413 (Dirk in #1422 ) The heuristic whether to run all available tests was refined (Dirk in #1434 addressing #1433 ) Coverage has been tweaked via additional #nocov tags (Dirk in #1435 ) Non-release Changes: Two interim non-releases 1.1.0.8.1 and .2 were made in order to unblock CRAN due to changes in R-devel rather than Rcpp Changes in Rcpp release version 1.1.0 (2025-07-01) Changes in Rcpp API: C++11 is now the required minimal C++ standard The std::string_view type is now covered by wrap() (Lev Kandel in #1356 as discussed in #1357 ) A last remaining DATAPTR use has been converted to DATAPTR_RO (Dirk in #1359 ) Under R 4.5.0 or later, R_ClosureEnv is used instead of CLOENV (Dirk in #1361 fixing #1360 ) Use of lsInternal switched to lsInternal3 (Dirk in #1362) Removed compiler detection macro in a header cleanup setting C++11 as the minunum (Dirk in #1364 closing #1363 ) Variadic templates are now used onconditionally given C++11 (Dirk in #1367 closing #1366 ) Remove RCPP_USING_CXX11 as a #define as C++11 is now a given (Dirk in #1369 ) Additional cleanup for __cplusplus checks (Iñaki in #1371 fixing #1370 ) Unordered set construction no longer needs a macro for the pre-C++11 case (Iñaki in #1372 ) Lambdas are supported in a Rcpp Sugar functions (Iñaki in #1373 ) The Date(time)Vector classes now have default ctor (Dirk in #1385 closing #1384 ) Fixed an issue where Rcpp::Language would duplicate its arguments (Kevin in #1388 , fixing #1386 ) Changes in Rcpp Attributes: The C++26 standard now has plugin support (Dirk in #1381 closing #1380 ) Changes in Rcpp Documentation: Several typos were correct in the NEWS file (Ben Bolker in #1354 ) The Rcpp Libraries vignette mentions PACKAGE_types.h to declare types used in RcppExports.cpp (Dirk in #1355 ) The vignettes bibliography file was updated to current package versions, and now uses doi references (Dirk in #1389 ) Changes in Rcpp Deployment: Rcpp.package.skeleton() creates ‘URL’ and ‘BugReports’ if given a GitHub username (Dirk in #1358 ) R 4.4.* has been added to the CI matrix (Dirk in #1376 ) Tests involving NA propagation are skipped under linux-arm64 as they are under macos-arm (Dirk in #1379 closing #1378 ) Changes in Rcpp release version 1.0.14 (2025-01-11) Changes in Rcpp API: Support for user-defined databases has been removed (Kevin in #1314 fixing #1313 ) The SET_TYPEOF function and macro is no longer used (Kevin in #1315 fixing #1312 ) An erroneous cast to int affecting large return object has been removed (Dirk in #1335 fixing #1334 ) Compilation on DragonFlyBSD is now supported (Gábor Csárdi in #1338 ) Use read-only VECTOR_PTR and STRING_PTR only with R 4.5.0 or later (Kevin in #1342 fixing #1341 ) Changes in Rcpp Attributes: The sourceCpp() function can now handle input files with read-only modes (Simon Guest in #1346 fixing #1345 ) Changes in Rcpp Deployment: One unit tests for arm64 macOS has been adjusted; a macOS continuous integration runner was added (Dirk in #1324 ) Authors@R is now used in DESCRIPTION as mandated by CRAN, the Rcpp.package.skeleton() function also creates it (Dirk in #1325 and #1327 ) A single datetime format test has been adjusted to match a change in R-devel (Dirk in #1348 fixing #1347 ) Changes in Rcpp Documentation: The Rcpp Modules vignette was extended slightly following #1322 (Dirk) Pdf vignettes have been regenerated under Ghostscript 10.03.1 to avoid a false positive by a Windows virus scanner (Iñaki in #1331 ) A (large) number of (old) typos have been corrected in the vignettes (Marco Colombo in #1344 ) Changes in Rcpp 'hot-fix' release version 1.0.13-1 (2024-11-01) Changes in Rcpp API: Use read-only VECTOR_PTR and STRING_PTR only with with R 4.5.0 or later (Kevin in #1342 fixing #1341 ) Changes in Rcpp Deployment: Authors@R is now used in DESCRIPTION as mandated by CRAN Changes in Rcpp release version 1.0.13 (2024-07-11) Changes in Rcpp API: Set R_NO_REMAP if not already defined (Dirk in #1296 ) Add variadic templates to be used instead of generated code (Andrew Johnson in #1303 ) Count variables were switches to size_t to avoid warnings about conversion-narrowing (Dirk in #1307 ) Rcpp now avoids the usage of the (non-API) DATAPTR function when accessing the contents of Rcpp Vector objects where possible. (Kevin in #1310 ) Rcpp now emits an R warning on out-of-bounds Vector accesses. This may become an error in a future Rcpp release. (Kevin in #1310 ) Switch VECTOR_PTR and STRING_PTR to new API-compliant RO variants (Kevin in #1317 fixing #1316 ) Changes in Rcpp Deployment: Small updates to the CI test containers have been made ( #1304 ) Changes in Rcpp release version 1.0.12 (2024-01-08) Changes in Rcpp API: Missing header includes as spotted by some recent tools were added in two places (Michael Chirico in #1272 closing #1271 ). Casts to avoid integer overflow in matrix row/col selections have been added (Aaron Lun #1281 ). Three print format correction uncovered by R-devel were applied with thanks to Tomas Kalibera (Dirk in #1285 ). Correct a print format correction

README code{white-space: pre-wrap;} span.smallcaps{font-variant: small-caps;} span.underline{text-decoration: underline;} div.column{display: inline-block; vertical-align: top; width: 50%;} div.hanging-indent{margin-left: 1.5em; text-indent: -1.5em;} ul.task-list{list-style: none;} pre > code.sourceCode { white-space: pre; position: relative; } pre > code.sourceCode > span { display: inline-block; line-height: 1.25; } pre > code.sourceCode > span:empty { height: 1.2em; } .sourceCode { overflow: visible; } code.sourceCode > span { color: inherit; text-decoration: inherit; } div.sourceCode { margin: 1em 0; } pre.sourceCode { margin: 0; } @media screen { div.sourceCode { overflow: auto; } } @media print { pre > code.sourceCode { white-space: pre-wrap; } pre > code.sourceCode > span { text-indent: -5em; padding-left: 5em; } } pre.numberSource code { counter-reset: source-line 0; } pre.numberSource code > span { position: relative; left: -4em; counter-increment: source-line; } pre.numberSource code > span > a:first-child::before { content: counter(source-line); position: relative; left: -1em; text-align: right; vertical-align: baseline; border: none; display: inline-block; -webkit-touch-callout: none; -webkit-user-select: none; -khtml-user-select: none; -moz-user-select: none; -ms-user-select: none; user-select: none; padding: 0 4px; width: 4em; color: #aaaaaa; } pre.numberSource { margin-left: 3em; border-left: 1px solid #aaaaaa; padding-left: 4px; } div.sourceCode { } @media screen { pre > code.sourceCode > span > a:first-child::before { text-decoration: underline; } } code span.al { color: #ff0000; font-weight: bold; } /* Alert */ code span.an { color: #60a0b0; font-weight: bold; font-style: italic; } /* Annotation */ code span.at { color: #7d9029; } /* Attribute */ code span.bn { color: #40a070; } /* BaseN */ code span.bu { color: #008000; } /* BuiltIn */ code span.cf { color: #007020; font-weight: bold; } /* ControlFlow */ code span.ch { color: #4070a0; } /* Char */ code span.cn { color: #880000; } /* Constant */ code span.co { color: #60a0b0; font-style: italic; } /* Comment */ code span.cv { color: #60a0b0; font-weight: bold; font-style: italic; } /* CommentVar */ code span.do { color: #ba2121; font-style: italic; } /* Documentation */ code span.dt { color: #902000; } /* DataType */ code span.dv { color: #40a070; } /* DecVal */ code span.er { color: #ff0000; font-weight: bold; } /* Error */ code span.ex { } /* Extension */ code span.fl { color: #40a070; } /* Float */ code span.fu { color: #06287e; } /* Function */ code span.im { color: #008000; font-weight: bold; } /* Import */ code span.in { color: #60a0b0; font-weight: bold; font-style: italic; } /* Information */ code span.kw { color: #007020; font-weight: bold; } /* Keyword */ code span.op { color: #666666; } /* Operator */ code span.ot { color: #007020; } /* Other */ code span.pp { color: #bc7a00; } /* Preprocessor */ code span.sc { color: #4070a0; } /* SpecialChar */ code span.ss { color: #bb6688; } /* SpecialString */ code span.st { color: #4070a0; } /* String */ code span.va { color: #19177c; } /* Variable */ code span.vs { color: #4070a0; } /* VerbatimString */ code span.wa { color: #60a0b0; font-weight: bold; font-style: italic; } /* Warning */ Rcpp: Seamless R and C++ Integration Synopsis The Rcpp package integrates R and C++ via R functions and a (header-only) C++ library. All underlying R types and objects, i.e. , everything a SEXP represents internally in R, are matched to corresponding C++ objects. This covers anything from vectors, matrices or lists to environments, functions and more. Each SEXP variant is automatically mapped to a dedicated C++ class. For example, numeric vectors are represented as instances of the Rcpp::NumericVector class, environments are represented as instances of Rcpp::Environment , functions are represented as Rcpp::Function , etc … The Rcpp-introduction vignette (now published as a TAS paper ; an earlier introduction was also published as a JSS paper provides a good entry point to Rcpp as do the Rcpp website , the Rcpp page and the Rcpp Gallery . Full documentation is provided by the Rcpp book . Other highlights: The conversion from C++ to R and back is driven by the templates Rcpp::wrap and Rcpp::as which are highly flexible and extensible, as documented in the Rcpp-extending vignette. Rcpp also provides Rcpp modules, a framework that allows exposing C++ functions and classes to the R level. The Rcpp-modules vignette details the current set of features of Rcpp-modules. Rcpp includes a concept called Rcpp sugar that brings many R functions into C++. Sugar takes advantage of lazy evaluation and expression templates to achieve great performance while exposing a syntax that is much nicer to use than the equivalent low-level loop code. The Rcpp-sugar gives an overview of the feature. Rcpp attributes provide a high-level syntax for declaring C++ functions as callable from R and automatically generating the code required to invoke them. Attributes are intended to facilitate both interactive use of C++ within R sessions as well as to support R package development. Attributes are built on top of Rcpp modules and their implementation is based on previous work in the inline package. See the Rcpp-atttributes vignettes for more details. Documentation The package ships with ten pdf vignettes, including a recent introduction to Rcpp now published as a paper in TAS (and as a preprint in PeerJ ). Also available is an earlier introduction which was published as a JSS paper . Among the other vignettes are the Rcpp FAQ and the introduction to Rcpp Attributes . Additional documentation is available via the Rcpp book by Eddelbuettel (2013, Springer); see ‘citation(“Rcpp”)’ for details. Performance Rcpp follows the C++ motto of “you pay only for what you use” and imposes no run-time performance penalty: Rcpp outperforms related packages in direct comparison, see for example this repo for details . Compile-time performance can be tuned by selecting components. But it is also worth noting that use of ccache will (strongly) dominate all such possible component choices, we have previously recommended its use. Examples The Rcpp Gallery showcases over one hundred fully documented and working examples. The package RcppExamples contains a few basic examples covering the core data types. A number of examples are included, as are well over one thousand unit tests which provide additional usage examples. An earlier version of Rcpp, containing what we now call the ‘classic Rcpp API’ was written during 2005 and 2006 by Dominick Samperi. This code has been factored out of Rcpp into the package RcppClassic, and it is still available for code relying on the older interface. New development should always use this Rcpp package instead. Other usage examples are provided by packages using Rcpp. As of early July 2025, there are 3043 CRAN packages using Rcpp (corresponding to 13.6% of all packages, and 61.3% of packages containing compiled code), a further 271 BioConductor packages in its current release as well as an unknown number of GitHub, Bitbucket, R-Forge, … repositories using Rcpp. All these packages provide usage examples for Rcpp. The package is in widespread use and has been downloaded over 100.6 million times (per the partial logs from the cloud mirrors of CRAN). Installation CRAN Rcpp released on CRAN are carefully tested and curated. CRAN ensures they interoperate with all other CRAN package on all test environment. The released and tested versions are available via all mirrors of CRAN network, and can be installed from within R via install.packages ( "Rcpp" ) Release Candidates We generally make interim candidate releases available via the r-universe page . It provides a standard R repository which corresponds to the current main branch in the source repository. Both binary and source versions can be installed via install.packages ( "Rcpp" , repos = c ( "https://r