See https://stat.ethz.ch/pipermail/r-devel/2017-August/074746.html for the
origin of the example here.
That
pretty(c(-1,1)*1e300, n = 1e9, min.n = 1) gave 20 intervals, far from 1e9, but
pretty(c(-1,1)*1e300, n = 1e6, min.n = 1) gave 100 intervals
(on a machine), made me trace through the cod
2017-08-11 16:00 GMT+02:00 Martin Maechler :
>> Dmitriy Selivanov
>> on Fri, 11 Aug 2017 17:33:31 +0400 writes:
>
> > Hi mailing list and R-core. Could someone from R-core please help me to
> > create account in bugzilla? I would like to submit issue related to
> gc() to
>
Thanks Martin, I've received invitation and will create ticket soon.
Regarding issue - basically the problem is that on operating systems which
use glibc memory is not freed (R releases it, but system doesn't trim it).
Setting corresponding environment variable (MALLOC_TRIM_THRESHOLD_) doesn't
hel
> Dmitriy Selivanov
> on Fri, 11 Aug 2017 17:33:31 +0400 writes:
> Hi mailing list and R-core. Could someone from R-core please help me to
> create account in bugzilla? I would like to submit issue related to gc()
to
> wishlist.
I will create one.
Your previous e-mails
Hi mailing list and R-core. Could someone from R-core please help me to
create account in bugzilla? I would like to submit issue related to gc() to
wishlist.
Related context is here -
https://stat.ethz.ch/pipermail/r-devel/2017-July/074715.html
--
Regards
Dmitriy Selivanov
[[alternativ
It's probably better to make it a runtime error, but note that it's
not necessarily a bad idea to add attributes to singleton symbols.
Those are used in Emacs Lisp for a variety of purposes. They just need
strong conventions (part of that is that in Emacs many symbols are
prefixed with a "namespace
Thanks for spotting this issue. The short answer is yes, adding
attributes to a symbol is a bad idea and will be turned into a runtime
error soon. Maintainers of packages that add attributes to symbols have
been notified and some have already fixed their code.
At least in one case the packag
