On Mon 28 Jul 2025, 20:50 Dmitry Derepko, <xepo...@gmail.com> wrote: > > On Mon, Jul 28, 2025 at 3:26 PM Rob Landers <rob@bottled.codes> wrote: > >> >> Wouldn’t a better approach be to allow serializing/deserializing >> exceptions? >> >> — Rob >> > > It would look like another workaround to my case. Same as deserializing > data into a class to write into a private property. > The simpler the better: just allow users to set their own trace. Or not > set it at all. > > -- > Best regards, > Dmitrii Derepko. > @xepozz >
I still don't understand what real life use case this solves. Maybe you already explained it but I didn't get it. IMHO the trace should be set by the engine and it should not be possible to overwrite the getTrace method. >
