Deprecate multi-irb feature

Open
#653 10 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
ruby
Domain
cli

Research direction

Start by locating the implementations and command handling for irb, jobs, fg, and kill, then inspect how IRB versions and deprecations are managed. Done means those commands warn in the next minor release and are removed in v2.0.0, with the relevant tests updated.

Written by the indexing model from the issue text.

Description

enhancement

Plan

  • Print deprecation warnings on these commands: irb, jobs, fg, and kill in the next minor release
  • Completely remove those commands in v2.0.0

Reasons

  • It's concept highly overlaps with workspace commands like chws, pushws...etc.
  • It spawns a new thread for every new new session, which conflicts with the upcoming irb-debug integration
  • But most importantly, we can't find any practical use for this feature and the cost of maintaining its compatibility with other features is high
    • For example, it will require the solution of #650 to support multi-thread irb sessions too

Feedback wanted

If you use the multi-irb feature and don't want to see it deprecated from IRB, please leave a comment below to explain your use case of it. It will help us assess this plan.

Dominant language
Ruby
Stars
477
Forks
165
Avg merge
1d 19h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ruby/irb

All issues in ruby/irb

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.