Re: [Rd] Objects not gc'ed due to caching (?) in R's S3 dispatch mechanism

This has nothing to do with printing or dispatch per se. It is the result of an internal register (R_ReturnedValue) being protected. It gets rewritten whenever there is a jump, e.g. by an explicit return call. So a simplified example is new_foo <- function() { e <- new.env() reg.finalizer(e

Re: [Rd] Objects not gc'ed due to caching (?) in R's S3 dispatch mechanism

I'd like to emphasize that although Iñaki's example uses print(), it also happens with other S3 generics. Please note that each of the following examples might need to be run in a clean R session to work. === Here's an example that doesn't use S3 dispatch. The finalizer runs correctly. id

[Rd] Objects not gc'ed due to caching (?) in R's S3 dispatch mechanism

Hi, I initially opened an issue in the R6 repo because my issue was with an R6 object. But Winston (thanks!) further simplified my example, and it turns out that the issue (whether a feature or a bug is yet to be seen) had to do with S3 dispatching. The following example, by Winston, depicts the

Re: [Rd] Suggesting patch to link DOIs against secure resolver

Thank you, Martin. I feel very warmly welcomed to this ML :-) Happy Easter holidays, everyone and kind regards, Katrin __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] R Lapack – why a subset?

> Is the cost really so high as to preclude adding the remaining Lapack > routines to Rlapack? Updating Lapack Libraries shall not break compatibility, and rather provide bug fixes I guess. > the reason is that there would be a significant extra maintenance burden > consisting of things that is

Re: [Rd] R Lapack – why a subset?

Peter, Is there not already a significant maintenance burden from cherry-picking routines? From my own experience (https://bugs.r-project.org/bugzilla/show_bug.cgi?id=16482 ) this is a painful process. And while users may not call the

Re: [Rd] R Lapack – why a subset?

I'm not too happy with this either, but I believe the reason is that there would be a significant extra maintenance burden consisting of things that is not being used by R itself. In particular, complex math routines are little used and have historically caused a number of issues with correct ar

[Rd] Typo in src/extra/tzone/registryTZ.c

I stumbled upon a typo in a time zone name: Irtutsk should be Irkutsk. A patch is attached. I also checked that this is the only bug of its kind in this file, i.e., all the other Olson time zones occurring in the file can also be found in Unicode Common Locale Data Repository. - Mikko Korpela Ind

Re: [Rd] Suggesting patch to link DOIs against secure resolver

> Katrin Leinweber > on Sun, 25 Mar 2018 19:04:34 +0200 writes: > Dear Madams and Sirs, > because the DOI foundation recommends a new, secure resolver [1], I > wanted to suggest the attached patch. It > a) updates a static DOI link in the docu, > b) the code chunk