Skip to content

Conversation

eddelbuettel
Copy link
Member

@eddelbuettel eddelbuettel commented Aug 21, 2025

Closes #471
Closes #474

As described in #471, Armadillo upstream switched to C++14.

That is not viable at CRAN as minimal compilation standard as well over 200 packages explicitly set C++11 and need to switched over time. So as a transition, we also include the (most recent) version of the 14.6.* branch, currently 14.6.3, as a fallback that is used if C++11 compilation is detected.

That scheme has been tested across multiple rounds of reverse dependencies and works. 1 2

Footnotes

  1. We see one regression in one package (also seen with another compiler at CRAN) that appears fully unrelated to the Armadillo changes, but possibly related to C++14. We contacted upstream as we think the issue it at their end and plan to convince CRAN that this not a regression,

  2. The regression revealed a real bug (noted in Regression with Armadillo 15.0.0 -- and 14.6.* under Intel #474) leading to release 15.0.1. Yay for reverse-dependency checks.

@eddelbuettel eddelbuettel changed the title RcppArmadillo 15.0.0-1 with Armadillo 15.0.0 (and Armadillo 14.6.3 under C++11) RcppArmadillo 15.0.1-1 with Armadillo 15.0.1 (and Armadillo 14.6.3 under C++11) Aug 22, 2025
@eddelbuettel eddelbuettel merged commit c8b7901 into master Aug 22, 2025
2 checks passed
@eddelbuettel eddelbuettel deleted the feature/arma_15.0 branch August 22, 2025 12:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Regression with Armadillo 15.0.0 -- and 14.6.* under Intel Accommodating breaking upstream changes
1 participant