We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Add useFuture() instead of options(future=...) with the advantage of immediate validation and lookup, e.g.
useFuture()
options(future=...)
useFuture(lazy) useFuture("lazy") useFuture(eager) useFuture(c("lazy", "eager")[2])
But then, how to check which future is in use? Is there a better name than useFuture().
The text was updated successfully, but these errors were encountered:
What about plan(), which works for both setting and getting, e.g.
plan()
> plan(lazy) > plan("lazy") > plan() "lazy"
Also, make it easy to modify the default arguments of a future evaluator function, e.g.
plan(eager, local=FALSE)
Internally, this will do something like:
eager_tmp <- eager formals(eager_tmp)$local <- FALSE
Sorry, something went wrong.
Add plan() [#2]
a45158b
Now plan() uses local scoping to store the setting; options() are no …
96c884d
…longer used [#2]
lazy
No branches or pull requests
Add
useFuture()
instead ofoptions(future=...)
with the advantage of immediate validation and lookup, e.g.But then, how to check which future is in use? Is there a better name than
useFuture()
.The text was updated successfully, but these errors were encountered: