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

Make sure we a good definition of Plate values #4

Description

@seagreen

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions