purescript / purescript/pursuit
Port project to PureScript?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 174
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
spago is being rewritten in PureScript so it can reuse the code provided by the upcoming Registry. I was wondering if this infrastructure should follow suit.
More people might contribute because it's written in the language they're using as opposed to Haskell, which tends to have a higher setup curve simply because of the tooling and language extensions.
However, I'm not sure what other advantages and disadvantages there might be. This code does work, but the large list of issues shows that some TLC would be nice.
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 reviewing the existing Haskell implementation and the referenced Spago rewrite and upcoming Registry context. The issue names no files or tests; completion would require defining the scope, trade-offs, and feasibility of a PureScript port before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100