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
cbindlist(X) would feel more data.table and provide the same functionality; even as a simple wrapper to setDT(unlist(X, recursive = FALSE)) this could be a nice convenience tool.
Not sure if there's any scope for further speedup under the hood as well.
The text was updated successfully, but these errors were encountered:
Pretty neat! I don't think there's any concern for speed here.. But if one were to do cbindlist(X)[, col := new_val], then col from X would be updated as well. Probably documenting it would be sufficient..
Duly noted, always good to remind side effects of mutability.
Would it be possible for setDT to do this internally, i.e. for setDT(X) to work (and be equally by-reference as setDT(unlist(X, recursive = FALSE))? Does it make sense for setDT to become that flexible, if so?
Inspired by this SO Q&A:
https://stackoverflow.com/q/48333523/3576984
dplyr::bind_cols
syntax is appealingly clean.cbindlist(X)
would feel moredata.table
and provide the same functionality; even as a simple wrapper tosetDT(unlist(X, recursive = FALSE))
this could be a nice convenience tool.Not sure if there's any scope for further speedup under the hood as well.
The text was updated successfully, but these errors were encountered: