Well, that's embarrassing. Sorry for the noise on that front, everyone. I
misunderstood something from the aforementioned unrelated conversation I
was having, but not double checking is on me (I rarely use if else and when
I do I avoid that situation in my own code, which is why I didn't already
kn
> Suharto Anggono Suharto Anggono via R-devel
> on Sat, 26 Nov 2016 17:14:01 + writes:
> Just stating, in 'ifelse', 'test' is not recycled. As I said in "R-intro:
length of 'ifelse' result"
(https://stat.ethz.ch/pipermail/r-devel/2016-September/073136.html),
ifelse(conditio
I think that in doc/manual/R-intro.texi, "used a part of an even larger
expression" should be "used as part of an even larger expression".
Another suspected typo is in doc/manual/R-ints.texi, where "dialects of
TeX and used for different purposes" should probably be "dialects of TeX
are used f
I first answered to the email below in r-help, but as I did not see any
response, and it looks like a bug/unwanted behavior, I am also posting
here. I have observed this in RGui, whereas it seems not to happen in
RStudio.
Similar to OP, I sometimes have a problem with functions using the
prog
> Related to the length of 'ifelse' result, I want to say that "example of
> different return modes" in ?ifelse led me to perceive a wrong thing in the
> past.
> ## example of different return modes:
> yes <- 1:3
> no <- pi^(0:3)
> typeof(ifelse(NA,yes, no)) # logical
>
Martin, thanks for the good news and sorry for wasting your (and others
time) by not doing my homework and query bugzilla first (lesson learned!
).
I have tested the new implementation from R-devel and observe a semantic
difference when playing with the parameters:
# Test script 1
g <- "glob
Dear R-devel list,
Running the following example on a recent R-devel (here, 2016-11-22
r71672) shows that the byte compiler can cause some significant
performance drops (here, computation time increasing from 0.01s to 0.31s
...)
=
library(Matrix)
someMatrix <-
