[ https://issues.apache.org/jira/browse/ARROW-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francois Saint-Jacques resolved ARROW-6183. ------------------------------------------- Fix Version/s: 0.15.0 Resolution: Fixed Issue resolved by pull request 5144 [https://github.com/apache/arrow/pull/5144] > [R] Document that you don't have to use tidyselect if you don't want > -------------------------------------------------------------------- > > Key: ARROW-6183 > URL: https://issues.apache.org/jira/browse/ARROW-6183 > Project: Apache Arrow > Issue Type: Wish > Components: R > Reporter: James Lamb > Assignee: Neal Richardson > Priority: Minor > Labels: pull-request-available > Fix For: 0.15.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > I noticed tonight that several functions from the *tidyselect* package are > re-exported by *arrow*. Why is this necessary? In my opinion, the *arrow* R > package should strive to have as few dependencies as possible and should have > no opinion about which parts of the R ecosystem ("tidy" or otherwise) are > used with it. > I think it would be valuable to cut the *tidyselect* re-exports, and to make > *feather::read_feather()*'s argument *col_select* take a character vector of > column names instead of a "*tidyselect::vars_select()"* object. I think that > would be more natural and would be intuitive for a broader group of R users. > Would you be open to removing *tidyselect* and changing > *feather::read_feather()* this way? -- This message was sent by Atlassian Jira (v8.3.2#803003)