You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently forder takes a single atomic vector, list or data.table as input. But it'd be much useful for so many other internal functions if it'd also accept a list of data.tables.
If that were possible, for example, unique.data.table's function definition could be changed to:
unique.data.table<-function(x, ..., incomparables=, ) {
x=list(x, ...) # in R v3.1 or using data.table internal functions to not copy the list# rest of the code
}
This allows us to optionally obtaining the unique of a list of data.tables without having to rbind them first.
Even more, this is extremely useful for all the setops functions, issue #547. Specifically, this line - where crux of the computations happen could be made much more (memory + speed) efficient!
jangorecki
changed the title
forder should be able to deal with more than one data.table efficiently.
forderv should be able to deal with more than one data.table efficiently.
Apr 10, 2020
Currently
forder
takes a singleatomic vector
,list
ordata.table
as input. But it'd be much useful for so many other internal functions if it'd also accept a list of data.tables.If that were possible, for example,
unique.data.table
's function definition could be changed to:This allows us to optionally obtaining the
unique
of a list of data.tables without having torbind
them first.Even more, this is extremely useful for all the
setops
functions, issue #547. Specifically, this line - where crux of the computations happen could be made much more (memory + speed) efficient!Also could be useful in implementing #873.
The text was updated successfully, but these errors were encountered: