Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upApparent bug in max() when mixing scalars and NaN #1289
Comments
brian-brazil
closed this
in
#1290
Jan 6, 2016
This comment has been minimized.
This comment has been minimized.
|
|
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
peterbourgon commentedJan 6, 2016
exprmax(expr)Expected behavior: the largest scalar.
Actual behavior: nondeterminstically, either the largest scalar, or NaN.
Further notes:
topk(1, expr)is also nondeterministicmax(sort(expr)reliably returns NaNmax(sort_desc(expr))reliably returns the largest scalar (and is the workaround I'm using for now)