[ruby-core:71261] [Ruby trunk - Feature #11630] possibility to serialize Proc or Lambda

Issue #11630 has been updated by Hans Mackowiak.


about external variables, how do you see @vars?

for sample

~~~
a = 4
proc { a = 5 }.call
p a
~~~
does change a local variable and cant be serialized because of that and the binding

~~~
@a = 4
proc { @a = 5 }.call
p @a
~~~
is that true for this one too because of it? or is that not the problem?

what about using instance eval?

~~~
class A; attr_accessor :x; end
a = A.new
a.x = 4
pr = proc { @x = 5 }
a.instance_eval(&pr)

p a.x #=> 5 
~~~


what if its not doing it over binding but over parameters?

~~~
class A; attr_accessor :x; end
a = A.new
a.x = 4
proc {|b| b.x = 5 }.call(a)

p a.x #=> 5 
~~~

shouldn't that be allowed to serialized because it doesnt need a binding?

----------------------------------------
Feature #11630: possibility to serialize Proc or Lambda
https://bugs.ruby-lang.org/issues/11630#change-54634

* Author: Lionel PERRIN
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
It would create a reliable alternative to gems like https://github.com/ngty/sourcify and thus makes much easier to implement the ruby-spark gem (https://github.com/ondra-m/ruby-spark).

I assume that it implies the Proc API to include methods like: Proc#get_external_variables.

To keep a seamless behavior of a deserialized Proc, it is important to add also a method like: Proc#has_side_effect?. This method would be return true if the Proc modifies at least one of its parameters or one of the external variables. (I have the feeling that this development might be a duplicate for issues/6806)

One extra feature would be to have these two methods available for Method as well: Method#get_external_variables (returning the instance variables) and Method#has_side_effect?



-- 
https://bugs.ruby-lang.org/