From: "Eregon (Benoit Daloze)" Date: 2021-11-04T13:13:03+00:00 Subject: [ruby-core:105934] [Ruby master Feature#18276] `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)` Issue #18276 has been updated by Eregon (Benoit Daloze). byroot (Jean Boussier) wrote in #note-8: > Assuming I correctly understand how it would work, then yes it would be great to have it to replace lots of costly `instance_exec`. I don't think it would change anything performance-wise. The only thing is it's possible to pass a block to the called proc that way (https://bugs.ruby-lang.org/issues/18276#note-1, https://bugs.ruby-lang.org/issues/18276#note-3). ---------------------------------------- Feature #18276: `Proc#bind_call(obj)` same as `obj.instance_exec(..., &proc_obj)` https://bugs.ruby-lang.org/issues/18276#change-94475 * 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: