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
Apparently, the ufunc loop selector prefers to cast integers to float32 in this case, which is somewhat surprising. This may have to do with the fact that given an integer array as one of the first two arguments, there are still two possible loop choices, and deciding which to use would need considering appropriate scalar casting rules for the last two arguments. Note that if one of the last arguments is an array instead of a scalar, the dtype decision is as expected, so maybe this is an issue with scalar special cases.
The text was updated successfully, but these errors were encountered:
pv
changed the title
float32 has priority over float64 for integer ufunc inputs
float32 has priority over float64 for scalar integer ufunc inputs with other arrays
May 20, 2015
Consider this:
Apparently, the ufunc loop selector prefers to cast integers to float32 in this case, which is somewhat surprising. This may have to do with the fact that given an integer array as one of the first two arguments, there are still two possible loop choices, and deciding which to use would need considering appropriate scalar casting rules for the last two arguments. Note that if one of the last arguments is an array instead of a scalar, the dtype decision is as expected, so maybe this is an issue with scalar special cases.
The text was updated successfully, but these errors were encountered: