You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 27, 2024. It is now read-only.
Optional record values (in the sense that fields can be missing entirely, not just null)
A distinction between row types and record types
We'll open individual issues for some of these topics. This issue is for the big picture things: do we want Plate to stay close to Haskell/PureScript's type systems, or do we want to add features common in other schema systems like maximum and minimum integers?
The text was updated successfully, but these errors were encountered:
Should typeclasses go on this list? My impression is no, since I don't see a principled way to implement them. You could have class schemas, but since Plate doesn't have functions you couldn't write useful instances. And without everyone having access to the same instances the principles behind typeclasses fall apart.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This will hopefully stay fairly short.
null
)We'll open individual issues for some of these topics. This issue is for the big picture things: do we want Plate to stay close to Haskell/PureScript's type systems, or do we want to add features common in other schema systems like maximum and minimum integers?
The text was updated successfully, but these errors were encountered: