sign(NaN)
Issue #231
resolved
At present, Blaze produces 0 when given a NaN as an argument. In this case, Numpy (np.sign) produces a NaN instead. Would the be a more sensible behavior for Blaze?
Comments (5)
-
-
-
assigned issue to
-
assigned issue to
-
- changed status to open
-
- changed status to resolved
The feature has been implemented, tested, optimized, and documented as required. It is immediately available via cloning the Blaze repository and will be officially released in Blaze 3.6.
-
reporter Thanks!
- Log in to comment
Hi Steven!
Thanks a lot for the proposal. The idea is very reasonable and we'll try to implement the necessary modifications. Thanks again,
Best regards,
Klaus!