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.
Is the rationale for making values more complicated than type Value = Map String Value solid?
Can we find a principled distinction between things like sequences that we define as primitive values and other things like multisets that we don't?
Once we find a principle for determining what to make a primitive value, does it suggest any new primitives we should add (or old ones we should take away)?
The text was updated successfully, but these errors were encountered:
Values are currently defined in docs/specification.md.
Is the rationale for making values more complicated than
type Value = Map String Value
solid?Can we find a principled distinction between things like sequences that we define as primitive values and other things like multisets that we don't?
Once we find a principle for determining what to make a primitive value, does it suggest any new primitives we should add (or old ones we should take away)?
The text was updated successfully, but these errors were encountered: