It would be nice to put the abstract data.table interface in it's separate code base.
That abstract interface requires some basic operations to do it's work:
ncol(), nrow(), dim(), etc.
column_data(), filter(), slice(), group(), merge(), etc.
...many more...
The fstproxy object would be an implementation of all of these required methods. When the interface can be made abstract enough, we could separate it and put it in it's own package (e.g. data.table.interface) to be able to use it for other backends (SQL databases for example).
It would be nice to put the abstract
data.tableinterface in it's separate code base. That abstract interface requires some basic operations to do it's work:ncol(),nrow(),dim(), etc.column_data(),filter(),slice(),group(),merge(), etc.The
fstproxyobject would be an implementation of all of these required methods. When the interface can be made abstract enough, we could separate it and put it in it's own package (e.g.data.table.interface) to be able to use it for other backends (SQLdatabases for example).