> Kurt Hornik writes:
Should be fixed now.
Best
-k
> Ivan Krylov via R-devel writes:
> Indeed, apparently using which.min/which.max on the string encoding is
> not good enough. ? which.min says that x can also be
> an R object for which the internal coercion to ‘double’ works
>
> Ivan Krylov via R-devel writes:
Indeed, apparently using which.min/which.max on the string encoding is
not good enough. ? which.min says that x can also be
an R object for which the internal coercion to ‘double’ works
and I guess we found a case where it does not work.
I'll look into
В Sat, 27 Apr 2024 13:56:58 -0500
Jonathan Keane пишет:
> In devel:
> > max(numeric_version(c("1.0.1.1", "1.0.3.1",
> "1.0.2.1")))
> [1] ‘1.0.1.1’
> > max(numeric_version(c("1.0.1.1000", "1.0.3.1000",
> "1.0.2.1000")))
> [1] ‘1.0.3.1000’
Thank
I've noticed something in R devel which seems a little off and not the
behavior I see in 4.4.0 or earlier versions. With numeric_versions that
have long (>8 digit) final components max and min return the first element
and not the max or min:
In devel:
> max(numeric_version(c("1.0.1.1",
