Several CRAN packages changes Futureverse R options, e.g. future.globals.maxSize and future.rng.onMisuse. This may happen when one of their functions are called, or when the package is attached. Not pointing fingers at any particular package, here are a few examples illustrating the problem:
The problem with doing this is that it overrides whatever settings the R user has decided to use. Also, changing options like future.rng.onMisuse to "ignore" removes the RNG protection in other places.
Tasks
[x] Improve documentation to clarify that this is a no-no.
[x] Give examples how to temporarily set in function.
[ ] Investigate if this can be protected against automatically.
[ ] Investigate if this can be detected in revdep checks.
[ ] Manually scan CRAN for cases and report to package maintainers, e.g.
Issue
Several CRAN packages changes Futureverse R options, e.g.
future.globals.maxSize
andfuture.rng.onMisuse
. This may happen when one of their functions are called, or when the package is attached. Not pointing fingers at any particular package, here are a few examples illustrating the problem:The problem with doing this is that it overrides whatever settings the R user has decided to use. Also, changing options like
future.rng.onMisuse
to"ignore"
removes the RNG protection in other places.Tasks
future.globals.maxSize
: https://github.com/search?q=org%3Acran%20future.globals.maxSize+language%3Ar&type=codefuture.rng.onMisuse
: https://github.com/search?q=org%3Acran+future.rng.onMisuse+language%3Ar&type=code