WIP: Generalize properties to constraints #1025
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Merge first: #1029
In prototyping phase. Overall goal is to obviate the need for
:and
,:not
, and:fn
schemas, in particular because of their brittle generators. It also leads more more relevant error messages #1001.TODO
Ideas:
:or
property[:map {:or [:a :b :c]} ..]
:keys
to:keyset
:set
with the same properties for heterogeneous sets:map-of
with keyset constraints:keyset
to:and
.[:int {:> 5 :< 10}]
, easier to generate than[:and :int [:> 5] [:< 10]]
.:min
:max
constraints so they can participate in constraint resolution:double
:gen/min
:gen/max
into account earlier during solution generation:gen/and
:gen/or
etc?:string
constraints:dispatch
constraint