Make an RFC about algebraic data / complete matches
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 601
- Forks
- 74
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
In the Racket1 ecosystem, there are multiple incompatible ways that people try to define datatypes with a fixed number of variants and get warnings in consuming code that does not handle all cases. One of the earliest is define-datatype from plai. There should be a standard way to do this pattern that integrates nicely with standard structs/classes.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the incompatible datatype approaches described in the issue, including plai's define-datatype and integration with standard structs/classes. Done means producing an agreed RFC that specifies a standard fixed-variant datatype pattern and how consuming code reports incomplete matches.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100