Open mllg opened 4 years ago
Some quick comments/questions:
How soon do you want it?
It's on my todo list to extract several of the internal utility functions an export them in a 'future.chunks' package. This is then meant to support higher-level, map-reduce packages such as future.apply, doFuture, furrr, ... There are some design decisions to be made before future.chunks can be made available.
Until future.chunks is available, you're welcome to use make_rng_seeds()
from future.apply in {{mlr3}} via private, stealth imports hacks - I can make a note about this dependency. If you do, I'd like to ask you to be prepared to move to make use future.chunks when it's available.
What do you think?
It is not urgent, I can use getFromNamespace()
until someone from CRAN starts complaining. Happy to switch to future.chunks
as soon as it is available.
Would you consider exporting
make_rng_seeds()
so that we can use it in mlr3?