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

Repository metrics

Stars

1,724 stars (1,724 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

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

Research direction

Understand how the shrinking logic handles numeric range schemas, especially for edge cases like Double/MAX VALUE. The bug indicates that the shrink function produces Double/MAX VALUE for a schema that requires values strictly greater than Double/MAX VALUE, which is impossible. Investigate the generator and shrinker implementation for double numbers.

Tech stack

None

Domain

backend

Issue type

Bug

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

2

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

ClojureGit

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

70