Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
IRB already has several features that rely on rdoc, such as:
PerfectMatchedProc
show_doc
commandAnd we could use its pager more in the future too. So it makes sense to declare rdoc as a dependency instead of relying on the one bundled with Ruby.
How will this affect Rails?
TL;DR -
rdoc
will be installed as a gem in all environments, but won't be required outside ofrails console
usages. In production,rdoc
will only be required when IRB's document look-up commands are used because autocompletion is diabled.rdoc
as a gem along withirb
irb
in console_command.rb, which is not loaded unlessrails console
is run. So whatever IRB requires, includingrdoc
, won't be loaded outside ofrails console
.rdoc
. And consider Rails disables IRB's autocompletion in production,rdoc
won't be loaded unlessshow_doc
/help
commands are run.