Along the lines of calling R_CheckUserInterrupt() only onces in a while:
> OTOH, in the past we have had to *disable* R_CheckUserInterrupt()
> in parts of R's code because it was too expensive,
> {see current src/main/{seq.c,unique.c} for a series of commented-out
> R_CheckUserInterrupt() for su
Hi,
This does seem to be a bug in is(); I'll take a look. I'm curious
about what stopped you from using setOldClass(), since that seems to
be the most appropriate solution.
Michael
On Tue, May 2, 2023 at 2:59 PM Russell Almond wrote:
>
> I’m somewhat puzzled by the following bit of code on R 4.
On Tue, May 2, 2023 at 3:29 PM Martin Maechler
wrote:
>
> > Ivan Krylov
> > on Tue, 2 May 2023 14:59:36 +0300 writes:
>
> > В Sat, 29 Apr 2023 00:00:02 +
> > Dario Strbenac via R-devel пишет:
>
> >> Could save.image() be redesigned so that it promptly responds to
>
I’m somewhat puzzled by the following bit of code on R 4.2.3 (also R 4.2.2)
> df <- data.frame(x=1:3)
> is (df,"ANY")
[1] FALSE
This seem to be false when the first argument is any S3 class, while I would
think that “ANY” would be true for S3, S4 and reference classes, as well as
primitive type
> Ivan Krylov
> on Tue, 2 May 2023 14:59:36 +0300 writes:
> В Sat, 29 Apr 2023 00:00:02 +
> Dario Strbenac via R-devel пишет:
>> Could save.image() be redesigned so that it promptly responds to
>> Ctrl+C? It prevents the command line from being used for a number
В Sat, 29 Apr 2023 00:00:02 +
Dario Strbenac via R-devel пишет:
> Could save.image() be redesigned so that it promptly responds to
> Ctrl+C? It prevents the command line from being used for a number of
> hours if the contents of the workspace are large.
This is ultimately caused by serialize
