René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Changes in downstream packages required by #1402","articleBody":"PR #1402 addresses the long-standing issue #1247 by masking `Rf_error()` and preferring `Rcpp::stop()`.  A relatively small number of packages do need a minor adjustment each: often just a removal of an `#include \u003cR.h\u003e` which may mess with the `NO_REMAP` macro, or a simple re-run of `compileAttributes()`.  This issue will regroup these changes and is based on the 2025-11-04 reverse dependency run summarized [in this text file](https://github.com/RcppCore/rcpp-logs/blob/master/results/Rcpp-20251104.txt) as mention in [this comment](https://github.com/RcppCore/Rcpp/pull/1402#issuecomment-3488126548).\n\nThe checklist will be expanded \"in due course\" to record PRs (or emailed patches).\n\n#### Group 1:  Including `R.h` which is best avoided\n\nThis is an issue we should be more proactive about (as for example [RcppArmadillo is w.r.t. `Rcpp.h`](https://github.com/RcppCore/RcppArmadillo/blob/master/inst/include/RcppArmadillo.h#L24-L26) as it can lead to issues with re-definitions of `error()` as seen here.  It is usually both harmless, and without side-effects -- until it isn't. \nIt consists on removing `#include \u003cR.h\u003e` as well as any other R headers, which are already loaded by Rcpp safely. The change can be made anytime before or after we land the patch in Rcpp.\n\n- [ ] BayesProject: patch **emailed** 2025-12-21\n- [ ] GeneralizedWendland: patch **emailed** 2025-12-21\n- [ ] locStra: patch **emailed** 2025-12-21\n- [x] LOMAR: patch **emailed** 2025-12-21, on CRAN 2025-12-22\n- [ ] SAM: patch **emailed** 2025-12-21\n- [ ] TDA: patch **emailed** 2025-12-21\n\n#### Group 2: Use `-DRCPP_NO_MASK_RF_ERROR` if needed\n\nSome packages have a complicated-enough setup, possibly with other callbacks into R, making use of `Rf_error()` unavoidable.  In those cases a `#define` can be used to restore the status quo.  These package can apply the change anytime.\n\n- [ ] ggiraph: davidgohel/ggiraph/pull/343 filled 2025-12-22, merged 2026-01-16\n- [x] mmrm: openpharma/mmrm/pull/556 filled 2025-12-22, merged 2026-01-07, on CRAN 2026-01-08\n- [ ] RTMB: kaskr/RTMB/pull/78 filled 2025-12-22, fixed 2025-12-24\n- [ ] s2: r-spatial/s2/pull/292 filled 2025-12-22, merged 2025-12-31\n\n#### Group 3:  Use custom patch\n\nThis mostly consists of applying a custom manual patch that switches to `Rcpp::stop()`.\n\n- [x] cpr: dewittpe/cpr/pull/63 filled 2025-12-22, merged 2025-12-23, on CRAN 2026-01-08\n- [ ] VIC5: CUG-hydro/VIC5.R/pull/2 filled 2025-12-22\n\n#### Group 4: Re-run `compileAttributes()`\n\nPackages that defined an `Rcpp::interface(cpp)`  have a resulting `RcppExports.cpp` that checks for correct (function) pointers and calls `Rf_error()`.  An `compileAttributes()` re-run _once the PR has landed_ will fix this.  So these packages may be on hold until we make the change in Rcpp, likely right after the next release so early 2026.  They can however apply the patch we prepared if they use the current GitHub version of Rcpp.\n\n- [ ] BGVAR: run `compileAttributes()`, patch\n- [ ] coga: run `compileAttributes()`, patch\n- [ ] comat: run `compileAttributes()`, patch\n- [ ] dqrng: run `compileAttributes()`, patch\n- [x] itp: run `compileAttributes()`, patch; version 1.2.2 on CRAN 2026-01-10\n- [ ] meteoland: run `compileAttributes()`, patch\n- [ ] ravetools:  run `compileAttributes()`, patch\n- [ ] RcppSimdJson:  run `compileAttributes()`, patch\n- [ ] rrum:  run `compileAttributes()`, patch\n- [ ] rucrdtw: run `compileAttributes()`, patch\n- [ ] sf:  run `compileAttributes()`, patch\n- [ ] simcdm: run `compileAttributes()`, patch\n","author":{"url":"https://github.com/eddelbuettel","@type":"Person","name":"eddelbuettel"},"datePublished":"2025-11-11T01:40:55.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/1406/Rcpp/issues/1406"}