Skip to content
This repository has been archived by the owner on Jan 27, 2024. It is now read-only.

Make sure we a good definition of Plate values #4

Open
seagreen opened this issue May 19, 2017 · 0 comments
Open

Make sure we a good definition of Plate values #4

seagreen opened this issue May 19, 2017 · 0 comments

Comments

@seagreen
Copy link
Owner

Values are currently defined in docs/specification.md.

  1. Is the rationale for making values more complicated than type Value = Map String Value solid?

  2. 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?

  3. 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)?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant