-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
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
Be more specific in the help with memoization #77
Comments
This is a good point and I wonder if it's more than a documentation issue. It seems cumbersome and error-prone to have to restart your session. Would it work & make sense to read this option in the functions calling |
The problem is the way we implement memoization. Lines 4 to 10 in b98a6fe
Our initial goal was to make it as transparent as possible for users to use Should we have an overarching function (like Something in the line of: fd_chull <- function(...) {
if (requireNamespace("memoise", quietly = TRUE) &&
isTRUE(getOption("fundiversity.memoise", TRUE))) {
fd_chull_memoised(...)
} else {
fd_chull_unmemoised(...)
}
} |
fixes #71 and #77 --------- Co-authored-by: Hugo Gruson <[email protected]> Co-authored-by: Matthias Grenié <[email protected]>
A little connex to #71 but the current description of memoisation
fundiversity/R/fd_fric.R
Lines 34 to 41 in 2d19f5c
doesn't mention that the options should be used before load fundiversity.
Maybe it could also be good to mention when to use and not use memoisation.
The text was updated successfully, but these errors were encountered: