Closed etiennebacher closed 4 months ago
I would say that arrow
is covered for developers since it is built on cpp11
, but it may not be obvious to users.
Good idea. I'll try to include an example of this.
Note that this is also an issue for the
polars
package: pola-rs/r-polars#851. This package is not on CRAN, so I don't know if you want to add it to the list as well.
I'm happy to do that; do you a small example for how to do this?
Added arrow example, cf. commit 6c041c2. See also https://future.futureverse.org/articles/future-4-non-exportable-objects.html#package-arrow
Note that this is also an issue for the
polars
package: pola-rs/r-polars#851. This package is not on CRAN, so I don't know if you want to add it to the list as well.I'm happy to do that; do you a small example for how to do this?
I see that your https://github.com/pola-rs/r-polars/issues/851 enough for me to work on something.
I've added an example for polars too, cf. https://future.futureverse.org/articles/future-4-non-exportable-objects.html#package-polars
Thanks for the suggestions.
Wish or feature request
Hello, I recently ran into an issue about non-exportable external pointers when calling some
arrow
functions infuture_lapply()
. I think it would be useful to add this package to the list of packages with non-exportable objects:as_arrow_table()
creates only a pointer to some data that is not actually present in R. The user can then perform some operations before pulling the data in R. I'm not anarrow
expert so here are more docs about this: https://arrow.apache.org/docs/r/articles/data_objects.htmlRelated to https://github.com/apache/arrow/issues/40231
Note that this is also an issue for the
polars
package: https://github.com/pola-rs/r-polars/issues/851. This package is not on CRAN, so I don't know if you want to add it to the list as well.Thanks