r2evans commented on issue #44306:
URL: https://github.com/apache/arrow/issues/44306#issuecomment-2405734186
I suspect a PR that does no more than
```diff
diff --git a/NAMESPACE b/NAMESPACE
index 412d70e..e18a425 100644
--- a/NAMESPACE
+++ b/NAMESPACE
@@ -407,6 +407,7 @@ export(uint32)
export(uint64)
export(uint8)
export(unify_schemas)
+export(unregister_binding)
export(unregister_extension_type)
export(utf8)
export(value_counts)
diff --git a/R/dplyr-funcs.R b/R/dplyr-funcs.R
index c0eb47e..507b51d 100644
--- a/R/dplyr-funcs.R
+++ b/R/dplyr-funcs.R
@@ -75,6 +75,7 @@ register_binding <- function(fun_name,
invisible(previous_fun)
}
+#' @export
unregister_binding <- function(fun_name) {
unqualified_name <- sub("^.*?:{+}", "", fun_name)
previous_fun <- .cache$functions[[unqualified_name]]
```
is the bare-minimum, but could spark some architecture discussion. For
instance, to me it makes sense to document both `register_binding` and
`unregister_binding` together, but the former is marked as `@keywords
internal`, likely for a reason.
Perhaps the practical aspects of having extraneous functions added to the
list of available scalar-functions is more a theoretical discussion than one
with practical implications. Having now seen `unregister_binding` confirms in
my head that it _is_ as simple as `<- NULL`-removing it from the internal list,
so I'm more comfortable with this understanding of how/where it's stored.
Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
