We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since type can only define sum(or) type let's use type or keyword instead, to make it explicit.
type
type or
Or maybe:
And type - zero and more values type alias Or type - zero and more variants type or Opaque type - basically wrapper around one value type opaque
type alias
type opaque
The text was updated successfully, but these errors were encountered:
Thanks for reporting this! To set expectations:
Finally, please be patient with the core team. They are trying their best with limited resources.
Sorry, something went wrong.
To me it seems somewhat confusing to call single-variant types "or":
type or Email = Email { local : Local, domain : Domain }
that is how it works now, it it still an or type with one variant
but that is another topic: if or type can have only one variant
I would suggest following:
That also solves a problem how data should be serialized into text/binary format.
Now, it is not clear if: Or type with one variant should be treated as just the value or variant index and the value.
No branches or pull requests
Since
type
can only define sum(or) type let's usetype or
keyword instead, to make it explicit.Or maybe:
And type - zero and more values
type alias
Or type - zero and more variants
type or
Opaque type - basically wrapper around one value
type opaque
The text was updated successfully, but these errors were encountered: