Is it okay to load bindrcpp to avoid the "warning message" though I'm not using it?

General
1

I've posted about the issue before, but I always get an annoying

Warning message:
package ‘bindrcpp’ was built under R version 3.4.4

message after I load the tidyverse.

Is it a bad idea to just load bindrcpp explicitly with library(bindrcpp) to avoid getting these warnings?

It doesn't seem like bindrcpp has any dependencies that aren't already loaded with the tidyverse, and no functions are getting masked.

2

You can use suppressWarnings() to, well, suppress warnings.

2 Likes
3

Your current version of R

R.version.string

is newer than the R version used to build bindrcpp. The solution is to reinstall bindrcpp. Almost always, it doesn't matter about the differing versions, but there are always edge cases. My general rule, is if the second number differs, e.g. R3.5 vs R3.4 I would reinstall. It doesn't take that long.

Is it a bad idea to just load bindrcpp explicitly with library(bindrcpp) to avoid getting these warnings?

For the reason above, I don't see why this would work.

As @mara mentioned, you can use suppressWarnings(). However, I try to never use this and instead fix the issue at the source.

3 Likes