We had this issue reported for lme4; it has also been reported here. Basically, if there is a mismatch between the installed binary version of Rcpp and RcppEigen, warnings and errors are possible.
Is it worth the hassle to implement a check (as glmmTMB does for the TMB binary version and TMB does for the Matrix binary version) to give an informative warning telling the user that they need to re-install a compatible stack?
(The advice given in the threads is to update Rcpp, but AFAICT the important thing is to have the versions of Rcpp and RcppEigen match, not necessarily to have an updated version of Rcpp ...)
We had this issue reported for
lme4
; it has also been reported here. Basically, if there is a mismatch between the installed binary version ofRcpp
andRcppEigen
, warnings and errors are possible.Is it worth the hassle to implement a check (as
glmmTMB
does for theTMB
binary version andTMB
does for theMatrix
binary version) to give an informative warning telling the user that they need to re-install a compatible stack?(The advice given in the threads is to update Rcpp, but AFAICT the important thing is to have the versions of Rcpp and RcppEigen match, not necessarily to have an updated version of Rcpp ...)