luckyframework / luckyframework/lucky_task
tmp/task_binary is recompiled unnecessarily before many tasks
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 8
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
The `tmp/tasks_binary` is recompiled before every task, as far as I can tell. It is often not necessary. If the source has not been modified since the binary was generated, there should not be a recompile. To determine this, parse the `require` statements in the source files, and nothing else, and `stat` the files for their modification dates. There are macro methods of receiving external input that could make the source stale, but they are rare and not worth checking.
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 at the task compilation path that produces tmp/tasks_binary and trace how source files are discovered before each task runs. Inspect the require statements and file modification times used for the decision; done means unchanged sources no longer trigger recompilation while modified required files still do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100