Split/fork off racc-compiler
Open
Nobody has claimed this yet.
- Dominant language
- Yacc
- Stars
- 569
- Forks
- 93
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 4
Description
Right now dependencies on the compiler are screwed over by racc (runtime) having a faux-gemspec that ships with ruby. Splitting out the compiler would make it trivial to have a developer dependency on the compiler and a runtime dependency on the regular racc gem.
I'm (very) happy to do the work to split it out if this is approved.
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 files or tests are named. Start by reviewing how the faux-gemspec and the runtime/compiler pieces are packaged; define the split so developers can depend on the compiler while runtime users depend on racc, then verify both dependency paths work independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100