Launch another Ruby Interpreter when IRB is started
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 478
- Forks
- 158
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 12
Description
from https://github.com/ruby/irb/pull/254#issuecomment-871698900
Separation running and input interpreters sounds good. But I know it's never easy.
At first I can do is creating issue so I do.
Expected benefits
- Running something(ex compiling) to check the code on background does not effect the input interpreter
- Reduce
requre - maybe something more...
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 by reading the linked discussion in ruby/irb#254, especially the referenced issue comment, to understand the proposed separation between running and input interpreters. The issue does not name files or tests; done would require defining and implementing that separation while preserving the stated background execution and reduced require benefits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100