data.table: another non-exportable object. #563
-
Thank you Henrik for your generosity in developing and sharing this package. I discovered another non-exportable object. library(data.table) doFuture::registerDoFuture() This gives me what I'm expecting. a three row, two column data.table, each cell a data.table:o <- rbindlist(o) This returns an error:o <-
I got %dopar% to work by using tibble's instead of data.tables.My problem is that most of my functions return data.table's.o <- rbindlist(o) I'm not sure you can do anything about it. ~Jim |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi. I think you have: options(future.globals.onReference = "error") set when doing this, cf. Section 'Packages that rely on external pointers' of the 'Non-Exportable Objects' vignette mentions data.table as a special type of objects holding "external pointers" but still can be exported (back and forth). I hope this helps PS. Please have a look at https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax on how to format your code examples here in GitHub to make them easier to read. |
Beta Was this translation helpful? Give feedback.
Hi. I think you have:
set when doing this, cf.
?future::future.options
. Because without that set, the future framework will not look for "non-exportable reference" and therefore not throw an error in this case.Section 'Packages that rely on external pointers' of the 'Non-Exportable Objects' vignette mentions data.table as a special type of objects holding "external pointers" but still can be exported (back and forth).
I hope this helps
PS. Please have a look at https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax on how to format your code examples here i…