Opaque `such-that` error when using `##NaN` as bound

Repository metrics

Stars

1,724 stars (1,724 stars)

PR merge metrics

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

Description

(mg/generate [:>= ##NaN])
;Couldn't satisfy such-that predicate after 10 tries.
(mg/generate [:> ##NaN])
;Couldn't satisfy such-that predicate after 10 tries.
(mg/generate [:< ##NaN])
;Couldn't satisfy such-that predicate after 10 tries.
(mg/generate [:<= ##NaN])
;Couldn't satisfy such-that predicate after 10 tries.
(mg/generate [:double {:max ##NaN}])
;Couldn't satisfy such-that predicate after 10 tries.

Contributor guide

Research direction

Investigate how NaN is handled in the such that predicate and add a check to produce a clearer error message.

Tech stack

None

Domain

developer experience

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.

Active

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

Clear

Prerequisites

Git

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

65