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
From shikokuchuo/mirai#37, it will be much faster for crew than mirai::unresolved() when the task data is large.
crew
mirai::unresolved()
The text was updated successfully, but these errors were encountered:
This means I can remove the n argument from collect() with no loss of efficiency!
n
collect()
Sorry, something went wrong.
Thinking about how to manage this back-compatibly. Maybe I want to grab the function only if it exists in nanonext:
nanonext
if (exists(x = ".unresolved", envir = getNamespace(name = "nanonext"))) { mirai_unresolved <- eval(expr = parse(text = "nanonext::.unresolved")) } else { mirai_unresolved <- nanonext::unresolved }
The eval(parse()) is to hide from the R CMD check static code analyzer.
eval(parse())
R CMD check
Then when the next nanonext is released, I can revert this workaround and require that version of nanonext.
b788f6d
5c046c9 moves entirely to .unresolved() and requires the recently released version 0.8.1 of nanonext.
.unresolved()
wlandau
No branches or pull requests
From shikokuchuo/mirai#37, it will be much faster for
crew
thanmirai::unresolved()
when the task data is large.The text was updated successfully, but these errors were encountered: