Hi.
Currently you cannot serialize a closure. That certainly makes sense.
But would it be possible/feasible that a closure could be serialized
if the value returned was the byte code used by the engine to execute
the compiled closure?
Or is this one of the don't go there ideas I sometimes get?
On 07.04.2009, at 09:55, Richard Quadling wrote:
Hi.
Currently you cannot serialize a closure. That certainly makes sense.
But would it be possible/feasible that a closure could be serialized
if the value returned was the byte code used by the engine to execute
the compiled closure?
Or is
Although this may open a lot of pitfalls, I'd support the idea to
serialize Closures.
My concern is about recovering a Closure from a user-persisted state.
People are able to do weird things, and we should be aware of that.
Just need to keep in mind of a dictate that says: Never underestimate
the
Hi,
On Tue, 2009-04-07 at 10:38 +0200, Lukas Kahwe Smith wrote:
Currently you cannot serialize a closure. That certainly makes sense.
[...]
I guess its a dont go there thing, as you also run into trouble with
use-d variables.
In the long run, I guess, we should try to reach it. Ignoring
