Incorrect handling of ##NaN with min/max

Description

None

Environment

We should replicate the behavior of Clojure here which has special handling for these cases.

Activity

Show:

David NolenFebruary 17, 2025 at 5:25 PM

We can probably resolve this one independently of . We should just manually type hint the return of the isNaN calls. Unfortunately the persistent collections rely on the current min/max. We should rename the inlining macros to something else like min*/max* or maybe unchecked-min , unchecked-max to discourage normal usage.

David NolenFebruary 17, 2025 at 5:17 PM

See for the more fundamental issue.

Details

Assignee

Reporter

Priority

Created January 23, 2025 at 3:34 AM
Updated February 17, 2025 at 5:26 PM