Begin forwarded message:
> On Fri, May 31, 2013 at 1:11 PM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote:
>
>>
>>
>> On Fri, May 31, 2013 at 12:54 AM, Max Leske <maxleske(a)gmail.com> wrote:
>>
>>>
>>> Bump.
>>>
>>> Doesn't anybody feel that corrupt blocks are a problem? IMHO that's
>>> something that should *never* happen.
>>>
>>
>> But what's happening here is that the Fuel serializer is allowing the
>> serialization of blocks without serializing their outer context and method,
>> and later the reconstruction of blocks against the *wrong* version of a
>> method. This is a Fuel bug. IMO the right solution is for Fuel to
>> serialize the method of the block, and on reconstruction replace the
>> reconstructed method with the method in the system iff the reconstructed
>> method is the same as that in the system, but substitute the recinstructed
>> method if it differs from the system's version (or of course if the
>> system;s version is missing). this mimics the system's behaviour with
>> unbound methods, where e.g. a block holds onto a method and the code of a
>> class is recompiled, resulting iun that block holding onto an unbound
>> method.
>>
>
> Sorry, "without serializing their outer context and method" is wrong;
> "without serializing their method"
