Using setDF() within a function will not modify global object, while setDT() does?
Nobody has claimed this yet.
- #4901 by @OfekShilon — closed without merging
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by running the provided iris and fo() reprex to compare setDT() and setDF() inside and outside a function. Trace how each function affects the input and returned object; done means the documented workflow has consistent, verified behavior or the issue clearly explains the intended limitation.
Written by the indexing model from the issue text.
Description
Note: this was first asked on stack, but asking here as it seems highly technical?
I am converting back and forth from data.frame to data.table using a workflow like: setDT() + some data.table operation + setDF() (see this post). Using setDF() will correctly transform back my input into a data.frame.
However, when I use exactly the same code, but within a function, the input is not transformed back into an data.frame anymore after a setDF() call, while the output will still correctly be converted to a df. I guess this comes from am ambiguity at that point whether the object of setDF() refers to the local data within the function or the global data in the user workspace? Strangely, this does not happen to setDT()?
So how can I ensure that I can use the workflow setDT() + some data.table operation + setDF() within a function, and that setDF() modifies back the input to that function?
library(data.table)
data(iris)
## using setDF outside of function
setDT(iris)
iris[, Sepal.Length.Mean := mean(Sepal.Length), by = Species]
setDF(iris)
class(iris)
#> [1] "data.frame"
## using setDF within a function
fo <- function(df){
setDT(df)
df[, Sepal.Length.Mean := mean(Sepal.Length), by = Species]
setDF(df)
df
}
res <- fo(iris)
class(iris)
#> [1] "data.table" "data.frame"
Created on 2020-11-17 by the reprex package (v0.3.0)
- Dominant language
- R
- Stars
- 3.9k
- Forks
- 1.1k
- Avg merge
- 14h 4m
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Rdatatable/data.table
-
as.data.table() recurses without end on a survival::Surv object (or any data.frame carrying one) Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Rdatatable/data.table#7887 ·
-
consistency tests
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Rdatatable/data.table#7853 · 3 comments ·
-
internals
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Rdatatable/data.table#6938 · 1 comment ·
-
encoding fread
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Rdatatable/data.table#5179 · 8 comments ·
-
documentation programming
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Rdatatable/data.table#3199 · 3 comments ·
All issues in Rdatatable/data.table
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
beginners blocker
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enviPathR OpenBuild Error Build OK Build Warning policies-accepted pre-review precheck-passed
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Bioconductor/BiocContributions#207 · 6 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
datacarpentry/semester-biology#1255 ·