|
08:57
sena_kun joined
|
|||
| lizmat | and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2024/12/23/2024-...-the-dots/ | 11:57 | |
| Geth | MoarVM/serialize_vmexception_prints_its_message_and_backtrace: c54b36567a | (Timo Paulssen)++ | src/6model/reprs/MVMException.c More helpful error when a VMException object is serialized Until now, we just get the generic "missing serialize function" error, but to an end user, it is not meaningful or actionable. Instead, we give VMException a serialization function that outputs an error message that explains at least a little bit what went wrong, and more importantly spits out the exception's message as well as its backtrace. |
18:34 | |
| MoarVM/serialize_vmexception_prints_its_message_and_backtrace: b2316f7d18 | (Timo Paulssen)++ | src/6model/reprs/MVMException.c More helpful error when a VMException object is serialized Until now, we just get the generic "missing serialize function" error, but to an end user, it is not meaningful or actionable. Instead, we give VMException a serialization function that outputs an error message that explains at least a little bit what went wrong, and more importantly spits out the exception's message as well as its backtrace. |
18:53 | ||
|
18:56
Nicholas_ joined
18:58
Nicholas left
|
|||
| Geth | MoarVM/serialize_vmexception_prints_its_message_and_backtrace: d8c3512b4a | (Timo Paulssen)++ | 2 files More helpful error when a VMException object is serialized Until now, we just get the generic "missing serialize function" error, but to an end user, it is not meaningful or actionable. Instead, we give VMException a serialization function that outputs an error message that explains at least a little bit what went wrong, and more importantly spits out the exception's message as well as its backtrace. |
19:00 | |
|
19:28
bisectable6 left
19:32
bisectable6 joined
23:13
sena_kun left
|
|||
| Geth | MoarVM: ugexe++ created pull request #1879: Use 64 bit ints in decoder |
23:38 | |