Hello,
All of the funprog functions except Position() use match.fun() early
in the body of the function. (Filter() seems to rely on lapply() for
this, but the effect is the same.) In most cases this isn't a problem,
but I can't see why Position() shouldn't look something like
Position2 <- functio
Thank you for the prompt reply.
> There in not such a mechanism, yet, but can be added, at least for
> diagnostics.
For example, can R.version somehow contain the information?
> We could add support for configure.ucrt, which would take precedence
> over configure.win on the UCRT builds (like Mak
On 9/8/21 2:08 PM, Hiroaki Yutani wrote:
Hi,
Are there any proper ways to know whether the session is running on
the R that is built with the UCRT toolchain or not? Checking if the
encoding is UTF-8 might do the trick, but I'm not sure if it's always
reliable.
There in not such a mechanism,
Hi,
Are there any proper ways to know whether the session is running on
the R that is built with the UCRT toolchain or not? Checking if the
encoding is UTF-8 might do the trick, but I'm not sure if it's always
reliable.
Also, I'd like to know if there's any mechanism to detect the UCRT in
configu
