gren-lang / gren-lang/compiler
Cache compiled modules for `gren run --package`
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 503
- Forks
- 29
- PR merge metrics
- No merged PRs in 30d
Description
To speed things up when running gren run --package, we can compile to author.package.Module.version instead of app and then check if it exists before compiling.
We can't do this for modules in the local project since we can't account for code changes.
Contributor guide
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 with the implementation of gren run --package and trace where package modules are compiled to app. Check how compiled package modules can be stored under author.package.Module.version, while local-project modules continue compiling normally; done means repeated package runs reuse existing compiled modules without caching local-project code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cli, compilers, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100