You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am wondering if it has something to do with using Double.add.
I noticed in bisect that this execution goes all the way from do_arith to R_binary. The checks at the source code (first, snd) return false (which seems ok). Then it jumps straight to calling R_binary.
In R_binary it skips the checks for array (makes sense) and in this check it enters. It ends up calling real_binary (source) and ends ups performing this operation (coqR code)
The text was updated successfully, but these errors were encountered:
If I remember correctly, there was an issue with NA_real, which displays NaN or something like that.
We are messing with OCaml's nan to differenciate NA from NaN and I guess that OCaml doesn't like that (because of some optimisations?). I don’t think that this is too big an issue for now.
I am wondering if it has something to do with using
Double.add
.I noticed in bisect that this execution goes all the way from
do_arith
toR_binary
. The checks at the source code (first, snd) return false (which seems ok). Then it jumps straight to callingR_binary
.In
R_binary
it skips the checks for array (makes sense) and in this check it enters. It ends up callingreal_binary
(source) and ends ups performing this operation (coqR code)The text was updated successfully, but these errors were encountered: