|
00:51
sourceable6__ left,
sourceable6 joined
03:13
patrickb left,
patrickb joined
05:10
ugexe left,
ugexe joined
08:40
djinni` left
08:41
djinni` joined
10:14
linkable6 left
10:15
linkable6 joined
10:42
unicodable6 left,
unicodable6 joined
11:04
[Coke] left,
[Coke] joined
|
|||
| Geth | rakudo/lizmat-no-backtrace: 90fa043633 | (Elizabeth Mattijsen)++ | 2 files Add :no-backtrace named argument to die() Following up on: github.com/Raku/problem-solving/issues/59 that was discussed in the resolutions meeting of 21 Feb 2026. $ raku -e 'die "foo"' ... (5 more lines) |
11:29 | |
| rakudo: lizmat++ created pull request #6076: Add :no-backtrace named argument to die() |
|||
|
14:50
ShimmerFairy left,
ShimmerFairy joined
15:31
finanalyst joined
16:15
[Coke] left
|
|||
| ugexe | isn't it better to have parameters without `no` in them and just default the to the True value? | 17:30 | |
| :$backtrace = True | |||
| like if i explicitly want the backtrace i'd have to write :!no-backtrace which is not good | 17:32 | ||
|
17:34
lucs left
|
|||
| ugexe | hmm actually no i don't like this parameter idea | 17:34 | |
| if i pass an error object like X::Foo along with :$no-backtrace then no-backtrace doesn't do anything | |||
| a special exception object such as "X::UserMessage" (as was suggested in the problem solving issue) would avoid that | 17:37 | ||
| this isn't the greatest solution but i put this in the mainline of my code to control exceptions from `die` | 17:46 | ||
| CATCH { default { try { ::("Rakudo::Internals").?LL-EXCEPTION } ?? .rethrow !! .message.¬e; &*EXIT(1) } } | |||
| lizmat | X::UserMessage as a subclass of X::AdHoc, I assume ? | 17:57 | |
|
18:09
[Coke] joined
18:39
lucs joined
18:41
lucs left
19:05
lucs joined
|
|||
| japhb | "self does my role" is a sequence of tokens I never expected. Cool though. :-) | 19:40 | |
| lizmat | :-) | ||
|
20:57
finanalyst left
|
|||