-
Notifications
You must be signed in to change notification settings - Fork 79
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
naming of functions #11
Comments
Mmm, I have a slight preference to keep them united under |
I'd also prefer to keep it all the same. I think there is benefit to being able to keep names of steps the same. Otherwise I feel like we would spend a lot of energy explaining the differences (so people learn to use the right one) and I'm not sure that's the main thing we want to emphasize. Do others agree? |
That's a good point. As long as they always use those save 3 verbs, they should be in decent shape; we'll be able to hopefully write sufficient error messages within each to coax them into doing the right thing. |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
Instead of
generate()
with different types, would it be better to havesimulate()
,bootstrap()
andpermute()
just be separate functions? They are "verbs" after all... Wouldn't this make it even clearer what is happening?The text was updated successfully, but these errors were encountered: