search for: altclass

...potting this corner > case! > ? Mon, 13 May 2024 11:37:57 -0300 Ricardo Villalba > <rikivillalba at gmail.com> ?????: >> I track the messages to be coded here: >> https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/altclasses.c#L580 >> and here >> https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/seq.c#L102 > You may have noticed that one of these places lacks the > underscore that R uses as the translation keyword: it's > _(string) th...

...potting this corner > case! > ? Mon, 13 May 2024 11:37:57 -0300 Ricardo Villalba > <rikivillalba at gmail.com> ?????: >> I track the messages to be coded here: >> https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/altclasses.c#L580 >> and here >> https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/seq.c#L102 > You may have noticed that one of these places lacks the > underscore that R uses as the translation keyword: it's > _(string) th...

Dear Ricardo Villalba, Thank you for spotting this corner case! ? Mon, 13 May 2024 11:37:57 -0300 Ricardo Villalba <rikivillalba at gmail.com> ?????: > I track the messages to be coded here: > https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/altclasses.c#L580 > and here > https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/seq.c#L102 You may have noticed that one of these places lacks the underscore that R uses as the translation keyword: it's _(string) that looks up the translation of the string....

Dear Ricardo Villalba, Thank you for spotting this corner case! ? Mon, 13 May 2024 11:37:57 -0300 Ricardo Villalba <rikivillalba at gmail.com> ?????: > I track the messages to be coded here: > https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/altclasses.c#L580 > and here > https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/seq.c#L102 You may have noticed that one of these places lacks the underscore that R uses as the translation keyword: it's _(string) that looks up the translation of the string....

...x102c] > [New Thread 19940.0x329c] > [New Thread 19940.0x37dc] > warning: Invalid parameter passed to C runtime function. > > Program received signal SIGSEGV, Segmentation fault. > 0x000000006c72d206 in compact_intseq_Dataptr (x=0x12783350, > writeable=<optimized out>) at altclasses.c:169 > 169 altclasses.c: No such file or directory. Thanks, would you know which svn version this is? Tomas > > On Wed, 9 Sep 2020 at 17:03, Tomas Kalibera <tomas.kalibera at gmail.com> wrote: >> On 9/9/20 8:48 AM, Hugh Parsonage wrote: >>> I am unable to set...

On 9/9/20 8:48 AM, Hugh Parsonage wrote: > I am unable to set break or use gdb with any success when I use that version. > > On linux I would do R -d gdb but this gives "unknown option '-d' " > while gdb R.exe (in the same directory as the debug version) gives the > same output as before. > > I'm happy to help but I appreciate this list might not be the

...r > length(1:(R_XLEN_T_MAX + 1)) Error en 1:(R_XLEN_T_MAX + 1): el resultado seria un vector muy largo The last is the same as the second, but translated into spanish. I track the messages to be coded here: https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/altclasses.c#L580 and here https://github.com/r-devel/r-svn/blob/abe625945c4402cd2bb97b5a64e7469db3e904f0/src/main/seq.c#L102 -- ?DV! [[alternative HTML version deleted]]

...19940.0x638c] [New Thread 19940.0x102c] [New Thread 19940.0x329c] [New Thread 19940.0x37dc] warning: Invalid parameter passed to C runtime function. Program received signal SIGSEGV, Segmentation fault. 0x000000006c72d206 in compact_intseq_Dataptr (x=0x12783350, writeable=<optimized out>) at altclasses.c:169 169 altclasses.c: No such file or directory. On Wed, 9 Sep 2020 at 17:03, Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 9/9/20 8:48 AM, Hugh Parsonage wrote: > > I am unable to set break or use gdb with any success when I use that version. > > >...

...Thread 19940.0x329c] [New Thread 19940.0x37dc] warning: > Invalid parameter passed to C runtime function. > Program received signal SIGSEGV, Segmentation fault. > 0x000000006c72d206 in compact_intseq_Dataptr > (x=0x12783350, writeable=<optimized out>) at > altclasses.c:169 169 altclasses.c: No such file or > directory. > On Wed, 9 Sep 2020 at 17:03, Tomas Kalibera > <tomas.kalibera at gmail.com> wrote: >> >> On 9/9/20 8:48 AM, Hugh Parsonage wrote: > I am unable to >> set break or use gdb with any...

...19940.0x638c] [New Thread 19940.0x102c] [New Thread 19940.0x329c] [New Thread 19940.0x37dc] warning: Invalid parameter passed to C runtime function. Program received signal SIGSEGV, Segmentation fault. 0x000000006c72d206 in compact_intseq_Dataptr (x=0x12783350, writeable=<optimized out>) at altclasses.c:169 169 altclasses.c: No such file or directory. On Wed, 9 Sep 2020 at 17:03, Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 9/9/20 8:48 AM, Hugh Parsonage wrote: > > I am unable to set break or use gdb with any success when I use that version. > > >...

...0x329c] > > [New Thread 19940.0x37dc] > > warning: Invalid parameter passed to C runtime function. > > > > Program received signal SIGSEGV, Segmentation fault. > > 0x000000006c72d206 in compact_intseq_Dataptr (x=0x12783350, > > writeable=<optimized out>) at altclasses.c:169 > > 169 altclasses.c: No such file or directory. > > Thanks, would you know which svn version this is? > > Tomas > > > > > On Wed, 9 Sep 2020 at 17:03, Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > >> On 9/9/20 8:48 AM, Hugh Parson...

....3 Gb > which seems much better ... until I do find a bug, may again > only in the C code underlying .Internal(inspect(.)) : >> y <- -1e9:2e9 ; .Internal(inspect(y)) > @7d86ac0 13 INTSXP g0c0 [REF(65535)] Error: long vectors not supported yet: ../../../R/src/main/altclasses.c:139 >> Indeed, the purported "integer overflow" (above) does not happen. It is "only" a 'printf' related bug inside .Internal(inspect(.)) on Windows. *interestingly*, the above bug I've noticed on (64-bit) Linux does *not* show on Windows (64-bit),...

Hi, I would like to figure out the meaning of the return value of these two functions. Here are the default definitions I find from R source code: static int altreal_Is_sorted_default(SEXP x) { return UNKNOWN_SORTEDNESS; } static int altreal_No_NA_default(SEXP x) { return 0; } I guess the macro *UNKNOWN_SORTEDNESS *in *Is_sorted* and 0 in *No_NA *simply means unknown sorted/NA status of

...ap an ALTREP object. If we change n from 100 to 10 and check the internal again, alt2 will not get wrapped. This makes the problem even more difficult since we cannot predict when would the wrapper appear. Here is the source code for the wrapper: https://github.com/wch/r-source/blob/trunk/src/main/altclasses.c#L1399 Here is a working example if one can build the sharedObject package from https://github.com/Jiefei-Wang/sharedObject n=100 > x=runif(n) > so1=sharedObject(x,copyOnWrite = FALSE) > so2=so1 > so2[1]=10 > .Internal(inspect(so1)) > .Internal(inspect(so2)) Here is my sess...

I can only reproduce on Windows, but reliably (both 4.0.0 and 4.0.2): $> R --vanilla x <- c(0L, -2e9:2e9) # > Segmentation fault Tried to reproduce on Linux but the above worked as expected. Not an issue merely with the length of the vector; for example, x <- rep_len(1:10, 1e10) works, though the altrep vector must be long to reproduce: x <- c(0L, -1e9:1e9) #ok Segmentation

...better ... until I do find a bug, may again >> > only in the C code underlying .Internal(inspect(.)) : >> >> >> y <- -1e9:2e9 ; .Internal(inspect(y)) >> > @7d86ac0 13 INTSXP g0c0 [REF(65535)] Error: long vectors not supported yet: ../../../R/src/main/altclasses.c:139 >> >> >> >> Indeed, the purported "integer overflow" (above) does not >> happen. >> It is "only" a 'printf' related bug inside .Internal(inspect(.)) on Windows. >> >> *interestingly*, the above bug I've noti...

...2, KNOWN_UNSORTED = 0}; The default value there is NA_INTEGER (ie INT_MIN), indicating that there is no sortedness information. Currently, *_NO_NA effectively return a boolean, (even though the actual return value is int). This can be seen in the method we provide for compact sequences in altclasses.c: static int compact_intseq_No_NA(SEXP x) { #ifdef COMPACT_INTSEQ_MUTABLE /* If the vector has been expanded it may have been modified. */ if (COMPACT_SEQ_EXPANDED(x) != R_NilValue) return FALSE; #endif return TRUE; } (FALSE is a macro for 0, TRUE is a macro for 1). Think of the...

...... until I do find a bug, may again >> > only in the C code underlying .Internal(inspect(.)) : >> >> >> y <- -1e9:2e9 ; .Internal(inspect(y)) >> > @7d86ac0 13 INTSXP g0c0 [REF(65535)] Error: long vectors not supported yet: ../../../R/src/main/altclasses.c:139 >> >> >> >> Indeed, the purported "integer overflow" (above) does not >> happen. >> It is "only" a 'printf' related bug inside .Internal(inspect(.)) on Windows. >> >> *interestingly*,...

...: cannot allocate vector of size 37.3 Gb which seems much better ... until I do find a bug, may again only in the C code underlying .Internal(inspect(.)) : > y <- -1e9:2e9 ; .Internal(inspect(y)) @7d86ac0 13 INTSXP g0c0 [REF(65535)] Error: long vectors not supported yet: ../../../R/src/main/altclasses.c:139 >

...st one place where the difference between R_NilValue > and NULL is very important as of right now. The current design of the > ALTREP framework contract expects ALTREP methods that return a SEXP > to return C NULL when they fail (or decline) to do the requested > computation and the non-altclass-specific machinery should be run as > a fallback. The places where ALTREP methods are plugged into the > existing, general internals then check for C-NULL after attempting to > fast-path the computation via ALTREP. Any non-C-NULL SEXP, including > R_Nilvalue will be taken as an indicati...