From: "jeremyevans0 (Jeremy Evans)" Date: 2021-10-28T14:50:11+00:00 Subject: [ruby-core:105857] [Ruby master Feature#18276] `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)` Issue #18276 has been updated by jeremyevans0 (Jeremy Evans). I'm in favor of adding this method, and would like to see it support the following: ```ruby pr = ->(*a, **kw, &block) do # ... block.call(something) end pr.bind_call(obj, arg, kw: nil) do |something| # ... end ``` This would allow you to get the equivalent of `instance_exec`, but with passing a block to the proc being instance execed, which is not currently possible. ---------------------------------------- Feature #18276: `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)` https://bugs.ruby-lang.org/issues/18276#change-94395 * Author: ko1 (Koichi Sasada) * Status: Open * Priority: Normal ---------------------------------------- `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)` ```ruby proc_obj = proc{|params...| ...} obj.instance_exec(params..., &proc_obj) ``` is frequent pattern. ``` $ gem-codesearch 'instance_exec.+\&' | wc -l 9558 ``` How about to introduce new method `Proc#bind_call`? ```ruby class Proc def bind_call obj, *args obj.instance_exec(*args, &self) end end pr = ->{ p self } pr.bind_call("hello") #=> "hello" pr.bind_call(nil) #=> nil ``` It is similar to `UnboundMethod#bind_call`. ---- My motivation; I want to solve shareable Proc's issue https://bugs.ruby-lang.org/issues/18243 and one idea is to prohibit `Proc#call` for shareable Proc's, but allow `obj.instance_exec(&pr)`. To make shortcut, I want to introduce `Proc#bind_call`. `UnboundProc` is another idea, but I'm not sure it is good idea... Anyway, we found that there are many usage of `instance_exec(&proc_obj)`, so `Proc#bind_call` is useful not for Ractors. -- https://bugs.ruby-lang.org/ Unsubscribe: