move type identifiers from type representatives to members #38
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Avaq
approved these changes
May 10, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This specification currently reuses the type representatives defined in the Fantasy Land specification. In fantasyland/fantasy-land#315 I have proposed changing the property name from
'constructor'to'fantasy-land'. The proposal is likely to be accepted, at which point members of algebraic data types would need two different “type representatives” to be compatible with both specifications.A type identifier need not be defined on a type representative; attaching it to each member would work equally well. This pull request removes all references to type representatives, disentangling this specification from the Fantasy Land specification.