On Wed, Mar 31, 2010 at 10:25 PM, Stanislav Malyshev wrote:
> Hi!
>
>
> prevented. The short background of what I'm doing is serializing
>> backtraces
>> when errors occur so that I can better diagnose bugs my clients report.
>> But
>> when a closure is passed as a function parameter somewhere
Hi!
prevented. The short background of what I'm doing is serializing backtraces
when errors occur so that I can better diagnose bugs my clients report. But
when a closure is passed as a function parameter somewhere in the call tree,
things just flat out exlode with the error:
Hmm, serializin
Firstly, I'm not here to debate the merits or the how-to of serializing
closures. I'm here to address the current usability issues with how it is
prevented. The short background of what I'm doing is serializing backtraces
when errors occur so that I can better diagnose bugs my clients report. Bu