Bug #13264: Binding#irb does not work in context of frozen object

• Status: Closed
• Assignee: nobu (Nobuyoshi Nakada)
• Target version: -
• ruby -v: ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-linux]
• Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN

[rbjl (Jan Lelis)]

This works as expected (starts IRB):

$ ruby -r irb -e '"".instance_eval{ binding.irb }'

This throws an error:

$ ruby -r irb -e '"".freeze.instance_eval{ binding.irb }'

/home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb/extend-command.rb:199:in `extend_object': can't define singleton (TypeError)
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:413:in `extend'
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:413:in `initialize'
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:713:in `new'
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:713:in `irb'
	from -e:1:in `block in <main>'
	from -e:1:in `instance_eval'
	from -e:1:in `<main>'

Also fails, but slightly different error:

ruby -r irb -e 'Object.new.freeze.instance_eval{ binding.irb }'

/home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb/extend-command.rb:200:in `extend_object': can't modify frozen object (RuntimeError)
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb/extend-command.rb:200:in `extend_object'
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:413:in `extend'
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:413:in `initialize'
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:713:in `new'
	from /home/jan/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/irb.rb:713:in `irb'
	from -e:1:in `block in <main>'
	from -e:1:in `instance_eval'
	from -e:1:in `<main>'

[shyouhei (Shyouhei Urabe)]

• Status changed from Open to Assigned
• Assignee set to nobu (Nobuyoshi Nakada)

[jeremyevans0 (Jeremy Evans)]

This is still a bug in the master branch of irb. I've submitted a pull request to fix it by using a delegate: https://github.com/ruby/irb/pull/24

[aycabta (aycabta .)]

• Status changed from Assigned to Closed

This was fixed by the Pull Request above.