You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Neal Richardson (Jira)" <ji...@apache.org> on 2021/06/16 15:26:00 UTC

[jira] [Commented] (ARROW-12940) [R] Expose C interface as R6 methods

    [ https://issues.apache.org/jira/browse/ARROW-12940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364345#comment-17364345 ] 

Neal Richardson commented on ARROW-12940:
-----------------------------------------

In doing this, can you please also resolve the skipped test due to ARROW-13075?

> [R] Expose C interface as R6 methods
> ------------------------------------
>
>                 Key: ARROW-12940
>                 URL: https://issues.apache.org/jira/browse/ARROW-12940
>             Project: Apache Arrow
>          Issue Type: New Feature
>          Components: R
>            Reporter: Neal Richardson
>            Assignee: Jonathan Keane
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 5.0.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Similar to pyarrow's export_to_c and import_from_c methods. We have c++ wrappers like ImportRecordBatch but they aren't exported from the package namespace, so attaching them to the R6 objects would provide a way to do that. 
> Lifecycle management of the C pointers they read/write to (allocate/delete) is left outside of these methods (as it is in the non-exported wrappers today).
> export_to_c should be a method on an object. import_from_c should be a "class method" like {{$create()}}.
> Once this is done, we should inform duckdb of this so that they can remove their {{getFromNamespace()}} workaround.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)