`[:> Double/MAX_VALUE]` generates `Double/MAX_VALUE`

Description

(defn shrink [?schema]
  (-> (quick-check 1 (for-all [s (mg/generator ?schema)] false) {:seed 0})
      :shrunk
      :smallest
      first))

(= Double/MAX_VALUE
   (shrink [:> Double/MAX_VALUE])
   (shrink [:>= Double/MAX_VALUE]))
;=> true

(> Double/MAX_VALUE Double/MAX_VALUE)
;=> false
(>= Double/MAX_VALUE Double/MAX_VALUE)
;=> true

Contributor guide

Tech stack

None

Domain

tooling

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Clojureproperty based testingmalli library

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

60

Research direction

Investigate how the shrink function works for numeric schemas in malli. Look at the source files related to generators and shrinking, likely in the malli.core or malli.generator namespace. Understand why shrinking a value generated with :> Double/MAX VALUE does not produce a smaller value. The fix may involve adjusting the shrink logic to correctly handle boundary values like Double/MAX VALUE.