[ 
https://issues.apache.org/jira/browse/ARROW-15010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Keane updated ARROW-15010:
-----------------------------------
    Description: 
This came up in the comments of ARROW-14575, but would be helpful even without 
doing anything with the namespace: instead of {{nse_funcs <- ...}}, create a 
registry + function to register each function and then use that registry in 
place of {{nse_funcs}}. 

This will: 

* Give us a bit more freedom for defining bindings in separate files (though 
which nse_funcs+collate we could do the same). E.g. have one file per package
* Possibly give a place to add some documentation (though see ARROW-15011)

  was:
This came up in the comments of ARROW-14575, but would be helpful even without 
doing anything with the namespace: instead of {{nse_funcs <- ...}}, create a 
registry + function to register each function and then use that registry in 
place of {{nse_funcs}}. 

This will: 

* Give us a bit more freedom for defining bindings in separate files (though 
which nse_funcs+collate we could do the same). E.g. have one file per package
* Possibly give a place to add some documentation (though see XXX)


> [R] Create a function registry for our NSE funcs
> ------------------------------------------------
>
>                 Key: ARROW-15010
>                 URL: https://issues.apache.org/jira/browse/ARROW-15010
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: R
>            Reporter: Jonathan Keane
>            Priority: Major
>
> This came up in the comments of ARROW-14575, but would be helpful even 
> without doing anything with the namespace: instead of {{nse_funcs <- ...}}, 
> create a registry + function to register each function and then use that 
> registry in place of {{nse_funcs}}. 
> This will: 
> * Give us a bit more freedom for defining bindings in separate files (though 
> which nse_funcs+collate we could do the same). E.g. have one file per package
> * Possibly give a place to add some documentation (though see ARROW-15011)



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to