build: investigate long build time
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.5k
- Forks
- 202
- PR merge metrics
- No merged PRs in 30d
Description
I’ve noticed that goblin has a very long compile time, relatively speaking.
I’ve meant to look into this before whether there is something we can do about it (and also how to look into it).
Maybe this is something the rustc might be interested in? It doesn’t have a “lot” of lines of code, nor is it really very generic (aside from usage of scroll) so I’m wondering what’s the precise issue.
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
No file, test, or entry point is named. Reproduce goblin's long compile time, profile the build to identify the precise cause, and document whether a practical change is possible or whether the issue belongs with rustc.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100