You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Apache Arrow JIRA Bot (Jira)" <ji...@apache.org> on 2022/10/18 17:52:00 UTC

[jira] [Commented] (ARROW-12322) [R] Work around masking of data type functions

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

Apache Arrow JIRA Bot commented on ARROW-12322:
-----------------------------------------------

This issue was last updated over 90 days ago, which may be an indication it is no longer being actively worked. To better reflect the current state, the issue is being unassigned per [project policy|https://arrow.apache.org/docs/dev/developers/bug_reports.html#issue-assignment]. Please feel free to re-take assignment of the issue if it is being actively worked, or if you plan to start that work soon.

> [R] Work around masking of data type functions
> ----------------------------------------------
>
>                 Key: ARROW-12322
>                 URL: https://issues.apache.org/jira/browse/ARROW-12322
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: R
>            Reporter: Ian Cook
>            Assignee: Dragoș Moldovan-Grünfeld
>            Priority: Minor
>
> There are more than two dozen data type functions in the arrow package, and they are named very generically, so they represent a large surface area for potential masking problems, which are likely to occur in user environments, not in our CI. If these masking errors do occur, they will probably give frustratingly unhelpful error messages. This happened to me with {{rlang::string()}}. The error was:
> {quote}Error in is_integerish\(x\) : argument "x" is missing, with no default
> {quote}
> This can be worked around with some non-standard eval magic.
> I implemented a working version of this in [https://github.com/apache/arrow/pull/9952] but we removed it before merging that PR because there were questions about whether there was a better way to implement it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)