leostera / leostera/reason-design-patterns
Improvements on the interpreter pattern
Nobody has claimed this yet.
- Dominant language
- Reason
- Stars
- 572
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
Hello and again, thanks for this repo.
I really liked the interpreter pattern. However, I want to know more, and it is hard to google. Do you have some specific links about blog post that I can read? If you have, probably will be nice to add them to the article.
Also, it seems the syntax is outdated. It does not compile with any recent version of reasonml. Will you consider updating it?
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
Locate the interpreter pattern article in the repository and first check whether its Reason syntax compiles with a recent version. Identify authoritative links about the interpreter pattern and update the article so the examples compile; done means the links are included and the syntax works with a current Reason toolchain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100