-
-
Notifications
You must be signed in to change notification settings - Fork 264
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Import packages, don't depend on them #176
Comments
Thanks Hadley.
|
Are you using Rcpp modules? You shouldn't need to depend on Rcpp in most cases. |
Yeah, it is this issue RcppCore/Rcpp#168 |
I'll try and find some time to look into this in more detail. Would be nice if we could get a fix into Rcpp. I bet me and @wch can work it out between us. |
a temporary solution would be to import and reexport |
I've made this change in d531b6e and it seems to work in every situation except compiling the vignette automatically when multiple cores are used, whereupon it says
But that doesn't happen if cores = 1, or if I install the package without the vignettes and run a model manually with multiple cores, or even if I explicitly call tools::buildVignette(). Any ideas? I'm currently only using 1 core in the vignette. |
This was largely fixed for rstan 2.9.0 or maybe 2.8.2, but I believe the "fix" entails that downstream packages of rstan that come with |
Solution from stan-dev/rstan#176
Solution from stan-dev/rstan#176
Currently you have
Depends: Rcpp (>= 0.11.0), utils, inline, methods
, but these should all be moved into imports. It's bad practice (and not needed) to attach other packages to the search path when loading a package.The text was updated successfully, but these errors were encountered: