Return to range(x, ..., na.rm = FALSE) prototype for common speedup

The `range` generic doesn't separate out `x` and `...`, but splitting them out
lets us easily check whether we can skip a potentially-slow `vec_c` operation to
combine them.

Author: brookslogan

R/type-vctr.R

@@ -620,8 +620,10 @@ max.vctrs_vctr <- function(x, ..., na.rm = FALSE) {
 }
 
 #' @export
-range.vctrs_vctr <- function(..., na.rm = FALSE) {
-  x <- vec_c(...)
+range.vctrs_vctr <- function(x, ..., na.rm = FALSE) {
+  if (dots_n(...) != 0L) {
+    x <- vec_c(x, ...)
+  }
 
   if (vec_is_empty(x)) {
     return(vec_cast_or_na(c(Inf, -Inf), x))

tests/testthat/test-type-vctr.R

@@ -659,7 +659,7 @@ test_that("`min` and `max` either combine `x` and `...` or abort (#1372)", {
   expect_snapshot(max(rep(x, 5), y), error = TRUE, cnd_class = TRUE)
 })
 
-test_that("`range` combines `...` (#1372)", {
+test_that("`range` combines arguments as expected (#1372)", {
   x <- new_vctr(1)
   y <- new_vctr(3)
   z <- new_vctr(as.numeric(13:11))