-
Notifications
You must be signed in to change notification settings - Fork 19
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
Rethink "eager" vs. "lazy" #473
Comments
Or |
Or "cautious" and "daring"/"fearless"? |
We should be able to materialize only as long as the result size does not reach a certain size (number of rows/cells/bytes):
I'll go with "tether" because this is easy to search and replace later. |
@krlmlr so do you agree that with the current usage of "lazy" at the R and at the C levels, it sounds there are two levels of laziness? Did I understand this correctly? I think aligning the terms, on the R interface, with what dtplyr/dbplyr do, makes it easier for users to pick it up. |
Maybe the opportunity to create a diagram 😸 |
Yes, there's eager vs. lazy (duckplyr is always lazy, dplyr is eager), and tethered vs. untethered (restrictions of automatic materialization, eager is always untethered by design). |
I think a diagram would help then! Happy to help with the vignette but will need to ask more questions. |
The word "tethered" here would explain something that is potentially surprising for users, and at least require some thought on their side. So I'd recommend choosing a word that's fairly common so that a non native speaker who maybe doesn't know "tethered" does not get one more obstacle on their way to understanding the concept. Also "tethered" might be easy to mistype (thetered etc). Based on word frequency in Google's books corpus, "bound" sounds like a better choice but it has the drawback of being used for other things like limits. |
I find "strict" not specific enough. |
"frugal" is probably not common enough. |
prudent like cautious |
Already used elsewhere: https://duckdb.org/2024/04/02/duckplyr.html#eager-vs-lazy-materialization
Perhaps
auto_collect
? Orauto_mat
?The text was updated successfully, but these errors were encountered: