Repository navigation
Vignette for programmatic data.table (eval, get, etc) #4247
Description
Activity
Here is a very rough idea on what could be included in this vignette:
How can I pass arguments to ... in order to keep the interface identical to data.table directly
... i ...
... j ...
... by/keyby ...
How do create dynamic variable names in
j?By reference
anything else (such as aggregation)
Reacted by John MacKintosh- addedprogrammingparameterizing queries: get, mget, eval, envparameterizing queries: get, mget, eval, env
on Apr 5, 2020 - linked a pull request that will close this issueprogramming on data.table #4304
on Apr 7, 2020 This will be greatly helpful. Though I wish there will be more consistent syntax available first. Otherwise the vignette may just be too complex and user's options are still limited/not good enough.
@dracodoc note that there is PR for that, and vignette is here https://github.com/Rdatatable/data.table/blob/09e0499b55545ae15a83d4e9a0536b632f85a892/vignettes/datatable-programming.Rmd. You are welcome to provide feedback/review.
@jangorecki Thanks for the link! I read it briefly, it's more about the proposed new syntax with substitute2 and related usage. I was thinking the vignette would also include existing usage patterns (like
()..) for completeness.I was thinking to wait others to write on that, but if nobody has done it yet, I can try to summary what I learned, maybe as a draft to receive more comments and improvements.
In PR there is my comment about
...
Copying over a request for a vignette that touches on building programmatic data.table workflows:
https://twitter.com/El_Grund/status/1197189888334061570?s=20
we certainly mention this all the time in the issue tracker but I couldn't think of a comprehensive resource we offer (I know there is some stuff in the FAQ).