discussion: docs: improve documentation of prudence argument#589
discussion: docs: improve documentation of prudence argument#589
prudence argument#589Conversation
| Sys.setenv(DUCKPLYR_FALLBACK_COLLECT = 0) | ||
| ``` | ||
|
|
||
| Unlike traditional data frames, duckplyr defers computation until absolutely necessary, allowing DuckDB to optimize execution. |
There was a problem hiding this comment.
this is explained better in one of the sections.
There was a problem hiding this comment.
Yes, but is this sentence harmful here?
There was a problem hiding this comment.
It could be discouraging to have a first sentence that's "complicated".
| Thrifty duckplyr frames are a compromise between lavish and frugal, discussed further below. | ||
| Thrifty duckplyr frames are a compromise between lavish and frugal, discussed below. | ||
|
|
||
| ### Thrift |
There was a problem hiding this comment.
I found the previous location of this section a bit jarring.
There was a problem hiding this comment.
I want to give the readers time to digest "lavish" and "frugal".
There was a problem hiding this comment.
What happened to me when reading was that I saw it would be discussed later and thought, ok then. But when the "Thrift" section appeared, it felt misplaced.
|
|
||
|
|
||
| ### Enforcing DuckDB operation | ||
| ### Side effect: Enforcing DuckDB operation |
There was a problem hiding this comment.
It is an important section but also does not go with the flow of the rest of the vignette.
There was a problem hiding this comment.
Good point, moving to "fallback".
Later.
There was a problem hiding this comment.
In the PR where I edit the fallback vignette, I added a section about this but that refers to this vignette.
|
This is how benchmark results would change (along with a 95% confidence interval in relative change) if 00b4546 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
|
This would be easier to review in two PRs. Will split and review individually. |
|
Other commit now in #593. |
|
This is how benchmark results would change (along with a 95% confidence interval in relative change) if 3385047 is merged into main:
Further explanation regarding interpretation and methodology can be found in the documentation. |
f404f17 to
3f29cba
Compare
| Sys.setenv(DUCKPLYR_FALLBACK_COLLECT = 0) | ||
| ``` | ||
|
|
||
| Unlike traditional data frames, duckplyr defers computation until absolutely necessary, allowing DuckDB to optimize execution. |
There was a problem hiding this comment.
Yes, but is this sentence harmful here?
| The term "prudence" is introduced here to set a clear distinction from the concept of "laziness", and because "control of automatic materialization" is a mouthful. | ||
|
|
||
| ## Eager and lazy computation | ||
| ## DuckDB optimization: lazy evaluation |
There was a problem hiding this comment.
"lazy evaluation" is easy to confuse with how R handles arguments.
There was a problem hiding this comment.
oops, this should be "lazy computation", sorry.
| Thrifty duckplyr frames are a compromise between lavish and frugal, discussed further below. | ||
| Thrifty duckplyr frames are a compromise between lavish and frugal, discussed below. | ||
|
|
||
| ### Thrift |
There was a problem hiding this comment.
I want to give the readers time to digest "lavish" and "frugal".
|
|
||
|
|
||
| ### Enforcing DuckDB operation | ||
| ### Side effect: Enforcing DuckDB operation |
There was a problem hiding this comment.
Good point, moving to "fallback".
Later.
|
@copilot: Resolve conflicts. |
Co-authored-by: krlmlr <1741643+krlmlr@users.noreply.github.com>
|
Completely borked by Copilot. This is a "discussion-only" PR, not intended to be merged. |
prudence argumentprudence argument
Fix #508
And some other suggested changes for readability.