Displaying 6 results from an estimated 6 matches for "r85472".
2023 Nov 05
2
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...s broken by the changes for NA coercion to complex;
the breakage essentially comes from
c(NA, 0+1i)
# vs
c(as.complex(NA), 0+1i)
The former is the output we tested against; the latter is essentially (via
coerceVector() in C) what's generated by our data.table::shift()
However, these are now (r85472) different:
Im(c(NA, 0+1i))
# [1] NA 1
Im(c(as.complex(NA), 0+1i))
# [1] 0 1
The former matches the behavior of directly using NA_complex_:
Im(c(NA_complex_, 0+1i))
# [1] NA 1
On R4.3.2, they both match the NA_complex_ behavior:
Im(c(NA, 0+1i))
# [1] NA 1
Im(c(as.complex(NA), 0+1i))
# [1] NA...
2023 Nov 06
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...e breakage essentially comes from
> c(NA, 0+1i)
> # vs
> c(as.complex(NA), 0+1i)
> The former is the output we tested against; the latter is essentially (via
> coerceVector() in C) what's generated by our data.table::shift()
> However, these are now (r85472) different:
> Im(c(NA, 0+1i))
> # [1] NA 1
> Im(c(as.complex(NA), 0+1i))
> # [1] 0 1
> The former matches the behavior of directly using NA_complex_:
> Im(c(NA_complex_, 0+1i))
> # [1] NA 1
> On R4.3.2, they both match the NA_complex_ b...
2023 Nov 06
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...;
> the breakage essentially comes from
>
> c(NA, 0+1i)
> # vs
> c(as.complex(NA), 0+1i)
>
> The former is the output we tested against; the latter is essentially (via
> coerceVector() in C) what's generated by our data.table::shift()
>
> However, these are now (r85472) different:
>
> Im(c(NA, 0+1i))
> # [1] NA 1
> Im(c(as.complex(NA), 0+1i))
> # [1] 0 1
>
> The former matches the behavior of directly using NA_complex_:
>
> Im(c(NA_complex_, 0+1i))
> # [1] NA 1
>
> On R4.3.2, they both match the NA_complex_ behavior:
>...
2023 Nov 07
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...> c(NA, 0+1i)
> > # vs
> > c(as.complex(NA), 0+1i)
>
> > The former is the output we tested against; the latter is
> essentially (via
> > coerceVector() in C) what's generated by our data.table::shift()
>
> > However, these are now (r85472) different:
>
> > Im(c(NA, 0+1i))
> > # [1] NA 1
> > Im(c(as.complex(NA), 0+1i))
> > # [1] 0 1
>
>
> > The former matches the behavior of directly using NA_complex_:
>
> > Im(c(NA_complex_, 0+1i))
> > # [1] NA 1
>...
2023 Nov 08
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...i)
> >>
> >> > The former is the output we tested against; the latter is
> >> essentially (via
> >> > coerceVector() in C) what's generated by our data.table::shift()
> >>
> >> > However, these are now (r85472) different:
> >>
> >> > Im(c(NA, 0+1i))
> >> > # [1] NA 1
> >> > Im(c(as.complex(NA), 0+1i))
> >> > # [1] 0 1
> >>
> >>
> >> > The former matches the behavior of directly...
2023 Nov 09
1
c(NA, 0+1i) not the same as c(as.complex(NA), 0+1i)?
...t;>
>> >> > The former is the output we tested against; the latter is
>> >> essentially (via
>> >> > coerceVector() in C) what's generated by our data.table::shift()
>> >>
>> >> > However, these are now (r85472) different:
>> >>
>> >> > Im(c(NA, 0+1i))
>> >> > # [1] NA 1
>> >> > Im(c(as.complex(NA), 0+1i))
>> >> > # [1] 0 1
>> >>
>> >>
>> >> > The former matches t...