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
If either min or max is an array having a different data type than x, behavior is unspecified and thus implementation-dependent.
Clarified that behavior is only defined when x, min, and max resolve to arrays having the same data type.
It seems to me that this is a malformed test, and only cases where min and max are (or resolve to, but even that's a stretch per first condition) the type of x should be tested.
The text was updated successfully, but these errors were encountered:
Agreed, the 2024 spec clarification is pretty clear on arrays of different dtypes. There's also gh-339 which report issues for mixing float32 and float64. Here's a fix: gh-360
Per spec,
It seems to me that this is a malformed test, and only cases where
min
andmax
are (or resolve to, but even that's a stretch per first condition) the type ofx
should be tested.The text was updated successfully, but these errors were encountered: