Add reload command to re-load files loaded via require

[ahogappa]

Summary

Add reload command to IRB that reloads files loaded via require, require_relative, or autoload during an IRB session.

Motivation

When developing gems and debugging/testing with IRB, it's tedious to restart IRB every time you modify a file. This feature allows you to reload modified files without restarting the session.

Implementation

Uses Ruby::Box's sandboxed $LOADED_FEATURES to detect which files are loaded by require. The basic flow is:

1. When require is called from the IRB prompt, execute it inside a new Ruby::Box
2. Compare $LOADED_FEATURES before and after to detect newly loaded files
3. Track the detected Ruby files for later reloading
4. Load the files into the main environment using load (native extensions use require)
5. When reload command is executed, re-load all tracked files

Usage

Prerequisites

• Ruby 4.0+ with RUBY_BOX=1 environment variable
• IRB.conf[:RELOADABLE_REQUIRE] = true in your .irbrc

Example

# .irbrc
IRB.conf[:RELOADABLE_REQUIRE] = true

# In IRB session
irb> require 'mylib'
irb> MyLib.hello  # => "original"
# ... edit mylib.rb ...
irb> reload
Reloaded: /path/to/mylib.rb
irb> MyLib.hello  # => "modified"

Limitations

• Constant redefinition warnings will appear on reload (uses load internally)
• Native extensions (.so, .bundle) cannot be reloaded
• Files loaded via Ruby::Box#require directly are not tracked
• Context mode 5 (IRB running inside a Ruby::Box) is not supported
  • These could be implemented in future PRs if there's demand

[ahogappa]

The command name reload might be confused with Rails console's reload!. Consider alternatives like reload_requires or refresh.

[st0012]

I think the name should have box in it so users understand it's closely associated with that language feature.

[st0012]

We should mark this as experimental.
And this command should have detailed help_mesasge to explain what it's for and how to set things up to run it.

[st0012]

I think the name should have box in it so users understand it's closely associated with that language feature.

[st0012]

Can we not put these in CONF? It's already bloated with things unrelated configs. We shouldn't use this as a cache storage.

[st0012]

Can we avoid this old alias_method_chain style?