00:00 arkiuat joined 00:04 arkiuat left 00:21 arkiuat joined 00:26 arkiuat left, arkiuat joined 00:32 arkiuat left 00:51 arkiuat joined 00:55 annamalai joined 00:56 Aedil left 01:11 annamalai left, annamalai joined 02:06 hulk joined 02:07 kylese left 03:15 hulk left, kylese joined 03:36 sibl joined 04:52 sibl left 04:56 arkiuat left 04:57 arkiuat joined 05:02 arkiuat left 05:10 Aedil joined 05:18 arkiuat joined 05:23 guestll joined 05:27 vrurg_ joined 05:28 guestll left 05:29 vrurg left 05:59 guestll joined 06:25 Aedil left 06:29 sibl joined 06:45 guestll left 07:05 sibl left 07:19 sibl joined 07:58 arkiuat left 08:12 sibl left, sibl joined 08:14 arkiuat joined 08:18 Aedil joined 08:24 arkiuat left 08:33 sibl left 08:54 arkiuat joined 08:59 arkiuat left 09:13 arkiuat joined 09:19 arkiuat left 09:39 arkiuat joined 09:44 arkiuat left 10:13 arkiuat joined 10:33 sibl joined 10:52 Sgeo left 11:17 arkiuat left 11:30 arkiuat joined 11:34 arkiuat left 11:35 arkiuat joined 11:40 arkiuat left 11:54 sibl left 11:58 arkiuat joined 12:03 arkiuat left 12:09 merp left 12:21 arkiuat joined 12:26 arkiuat left 12:32 El_Che left 12:33 annamalai left, annamalai joined 12:34 El_Che joined 12:38 sibl joined 12:41 arkiuat joined 12:46 arkiuat left 13:17 arkiuat joined 13:21 arkiuat left 13:42 phogg left, arkiuat joined, phogg joined 13:43 coleman left 13:44 coleman joined 13:46 arkiuat left 14:08 arkiuat joined
antononcube - Why shouldn’t you eat too much pi? - You’ll end up with a big circumference. 14:09
(Some celebrate Pi-day today, 3/14.) 14:10
lizmat yeah... europeans like to be more accurate on 22 July :-)
14:13 arkiuat left
ugexe m: grammar { method TOP { <.asdfwqef> } }.new.parse("asdf") 14:22
camelia P6opaque: no such attribute '$!pos' on type Match in a Str when trying to get a value
in block <unit> at <tmp> line 1
ugexe weird error i encountered when trying to come up with an example of why i wish there was a way to catch method calls on method names that don't exist at compile time
14:37 lichtkind joined 14:43 arkiuat joined 14:48 arkiuat left 15:04 arkiuat joined 15:09 arkiuat left 15:34 arkiuat joined 15:37 david7832 joined 15:39 arkiuat left 15:57 sibl left 16:00 arkiuat joined 16:05 arkiuat left 16:08 arkiuat joined 16:12 david7832 left 16:13 arkiuat left 16:14 arkiuat joined, sibl joined 16:18 sibl left 16:23 arkiuat left 16:25 arkiuat joined 16:30 arkiuat left 16:31 arkiuat joined 16:49 arkiuat left 16:52 arkiuat joined 16:57 arkiuat left 17:24 arkiuat joined 17:26 librasteve_ joined 17:29 arkiuat left 17:46 arkiuat joined, gabiruh left, gabiruh joined 17:53 arkiuat left 18:06 arkiuat joined 18:15 arkiuat left 18:20 Aedil left
lizmat ugexe: just to be sure: that TOP was a "method" and not a rule / token / regex was intentional ? 18:30
because this looks like a case of DIHWIDT ?
18:31 arkiuat joined
lizmat re catching unknown methods: you *can* add a FALLBACK method to a grammar: docs.raku.org/language/typesystem#...K_(method) 18:34
18:36 arkiuat left 18:38 arkiuat joined 18:43 arkiuat left 18:44 arkiuat joined 18:56 arkiuat left 19:15 david7832 joined, david7832 left, ds7832 joined 19:18 arkiuat joined 19:24 arkiuat left 19:28 Sgeo joined 19:34 cm_ joined 19:36 cm left, cm_ is now known as cm 19:37 arkiuat joined 19:42 arkiuat left 19:48 arkiuat joined 20:10 arkiuat left 20:15 vrurg joined, vrurg_ left 20:22 arkiuat joined 20:35 arkiuat left 20:47 arkiuat joined 21:06 librasteve_ left
ugexe i don't need a fallback, i need to know the method name is e.g. typod without running into it at runtime 21:52
github.com/ugexe/Raku-Grammar--HTT...od#L37-L38 21:58
as an example there is <.IPv6addrz>, but on the next line you can see the actual method name is <.IPv6addr>
IPv6addz rather 21:59
obviously a test could catch such things, but huge grammars don't make that easy 22:00
instead i wish there was a way to mark a class as finalized such that no new methods can be added to it, which i presume would make it possible to get a no-such-method error much earlier 22:02
22:21 annamalai left
timo hm, is that not something that Comma can already do? it'd be a heuristic of course, but if you can make that assumption it's probably okay and gives helpful results? maybe not something for the compiler to warn about unless you want future raku code to be full of # ign:missing-method comments or whatever 23:22