search for: dtemplelang

...n*i > return(myfn) > }) > > sapply(test, function(myfn) myfn(2)) From: Jeroen Ooms <jeroenooms at gmail.com> > I think it is a bug. If we use substitute to inspect the promise, it > appears the index number is always equal to its last value: From: Duncan Temple Lang <dtemplelang at ucdavis.edu> > Not a bug, but does surprise people. It is lazy evaluation. I think it is indeed a bug. The lapply code saves a bit of time by reusing the same storage for the scalar index number every iteration. This amounts to modifying the R code that was used for the previous functio...

Janko and I have been in touch. This is, I believe, a Windows specific issue and a compilation issue. I could be wrong, but that is my impression from other reports. When I have time (?! :-)), I will deal with it. Hopefully this will be very soon. Thanks Janko. D. On 12/14/14, 7:54 PM, Jeroen Ooms wrote: > On Thu, Dec 11, 2014 at 12:13 PM, Janko Thyson > <janko.thyson at gmail.com

...gt;> >> sapply(test, function(myfn) myfn(2)) > > From: Jeroen Ooms <jeroenooms at gmail.com> >> I think it is a bug. If we use substitute to inspect the promise, it >> appears the index number is always equal to its last value: > > From: Duncan Temple Lang <dtemplelang at ucdavis.edu> >> Not a bug, but does surprise people. It is lazy evaluation. > > > I think it is indeed a bug. The lapply code saves a bit of time by > reusing the same storage for the scalar index number every iteration. > This amounts to modifying the R code that was us...

...gt;> >> >> From: Jeroen Ooms <jeroenooms at gmail.com> >> >>> I think it is a bug. If we use substitute to inspect the promise, it >>> appears the index number is always equal to its last value: >>> >> >> From: Duncan Temple Lang <dtemplelang at ucdavis.edu> >> >>> Not a bug, but does surprise people. It is lazy evaluation. >>> >> >> >> I think it is indeed a bug. The lapply code saves a bit of time by >> reusing the same storage for the scalar index number every iteration. >> Th...