[
https://issues.apache.org/jira/browse/ARROW-18148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17627230#comment-17627230
]
Stephanie Hazlitt commented on ARROW-18148:
-------------------------------------------
{quote}> "where do we talk about the nuance"
{quote}
One approach when making a big design change is to have a short vignette that
explains the change itself (e.g. [dbplyr 2.0 did
this|https://dbplyr.tidyverse.org/articles/backend-2.html]). What is proposed
is not a breaking change, however if the package moves to having
`read_arrow(..., format = c("file", "stream", "auto")) it might be worth a
101-level page on the function naming history, given there was an early version
of `read_arrow()` which was deprecated, the marketing that needs to be done re:
feather vs arrow naming and so on. This could also be done in the proposed
Arrow serialization vignette with pointers, as suggested.
> [R] Rename read_ipc_file to read_arrow_file & highlight arrow over feather
> --------------------------------------------------------------------------
>
> Key: ARROW-18148
> URL: https://issues.apache.org/jira/browse/ARROW-18148
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Documentation, R
> Reporter: Stephanie Hazlitt
> Priority: Minor
> Labels: feather
>
> Following up from [this mailing list
> conversation|https://lists.apache.org/thread/nxncph842h8tyovxp04hrzq4y35lq4xq],
> I am wondering if the R package should rename `read_ipc_file()` /
> write_ipc_file()` to `read_arrow_file()`/ `write_arrow_file()`, or add an
> additional alias for both. It might also be helpful to update the
> documentation so that users read "Write an Arrow file (formerly known as a
> Feather file)" rather than the current Feather-named first approach, assuming
> there is a community decision to coalesce around the name Arrow for the file
> format, and the project is moving on from the name Feather.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
