|
🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm Set by lizmat on 8 June 2022. |
|||
|
00:23
lizmat left,
Geth joined
|
|||
| librasteve_ | rakudoweekly.blog/2026/02/02/2026-...riodicity/ | 08:10 | |
|
10:01
lizmat_ left
10:02
lizmat joined
11:28
librasteve_ left
12:03
librasteve_ joined
12:07
rakkable left
12:08
rakkable joined
14:38
librasteve_ left
15:26
soverysour joined
18:20
librasteve_ joined
|
|||
| lizmat | hmmm... how do we actually distinguish CONTROL exceptions from runtime exceptions? ~~ Exception ?? | 18:52 | |
|
19:54
kjp left
20:11
soverysour left
|
|||
| lizmat | meh... looks like: | 20:27 | |
| m: say Any ~ "foo" | |||
| camelia | Use of uninitialized value of type Any in string context. Methods .^name, .raku, .gist, or .say can be used to stringify it to something meaningful. foo in block <unit> at <tmp> line 1 |
||
| lizmat | is actually handled by the: multi sub infix:<~>(*@args) { @args.join } candidate | 20:28 | |
| sometimes I wish we could export a CONTROL or a CATCH block | 20:53 | ||
| e.g. through an EXPORT sub, something like: sub EXPORT() { Map.new: '§CONTROL' => { when CX::Warn { .throw } } } | 20:54 | ||
| then we could put that in a module called "warnings-not-allowed" and then just put: "use warnings-not-allowed;" in your code / debugging session to have any warning stop execution immediately | 20:55 | ||
| [Coke] | stop execution == die or more like a skip? | 20:56 | |
| lizmat | like die | 21:00 | |
| skipping we already have with "quietly | |||
| nemokosch that's what .throw does? | |||
| afk& | 21:01 | ||
|
21:30
librasteve_ left
21:44
librasteve_ joined
|
|||
| [Coke] | lizmat: isn't 'use fatal' the other thing? | 22:40 | |
|
23:50
librasteve_ left
|
|||