Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Row types are poorly explained #374

Open
gdennie opened this issue Feb 18, 2021 · 3 comments
Open

Row types are poorly explained #374

gdennie opened this issue Feb 18, 2021 · 3 comments

Comments

@gdennie
Copy link

gdennie commented Feb 18, 2021

The Row type description begins...

A row of types represents an unordered collection of named types, with duplicates.

That description is unclear. By process of elimination it appears the types are what is allowed to be duplicated while the labels, as keys, cannot be duplicated. Perhaps a more plain wording is as follows:

A row is an unordered list of labels with type identifiers: Set (Tuple Label Type)

@natefaubion
Copy link
Contributor

natefaubion commented Feb 18, 2021

Set (Tuple Label Type) is not quite correct. It's more like Map Label (NonEmptyList Type). Set (Tuple Label Type) implies the ordering relation between the types is undefined, but that's not the case; there is a cons ordering.

@natefaubion
Copy link
Contributor

Probably more accurate, rows behave like scope.

@gdennie
Copy link
Author

gdennie commented Feb 18, 2021

I am still trying to find a succinct description... How about this?

A row is an unordered list of labels each identifying a nonempty list of types.

With respect to scope, are you saying that Rows provide a context with values as oppose to providing a schema for data storage?

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

No branches or pull requests

2 participants