|
00:05
arkiuat left
00:17
arkiuat joined
00:24
arkiuat left
00:40
arkiuat joined
00:46
arkiuat left
01:00
arkiuat joined
01:06
arkiuat left
01:17
arkiuat joined
01:22
arkiuat left
01:45
arkiuat joined
01:50
arkiuat left
02:00
arkiuat joined
02:05
arkiuat left
02:33
arkiuat joined
02:40
arkiuat left
03:12
arkiuat joined
03:17
arkiuat left
03:34
arkiuat joined
03:39
arkiuat left
03:57
arkiuat joined
04:01
arkiuat left
04:13
arkiuat joined
04:18
arkiuat left
04:44
arkiuat joined
06:04
arkiuat left
06:10
arkiuat joined
06:14
arkiuat left
06:44
arkiuat joined
06:49
arkiuat left
07:18
arkiuat joined
07:23
arkiuat left
07:36
arkiuat joined
07:40
arkiuat left
08:03
arkiuat joined
08:09
arkiuat left
08:37
arkiuat joined
08:43
arkiuat left
08:57
finanalyst left
09:12
arkiuat joined
09:17
arkiuat left
09:46
arkiuat joined
09:51
arkiuat left
10:19
arkiuat joined
10:24
arkiuat left
10:53
arkiuat joined
10:58
arkiuat left
11:06
finanalyst joined
11:27
arkiuat joined
11:32
arkiuat left
11:35
arkiuat joined
11:39
arkiuat left
11:43
librasteve_ left
12:06
arkiuat joined
12:11
arkiuat left
12:37
arkiuat joined
12:42
arkiuat left
12:59
arkiuat joined
13:04
arkiuat left
13:16
arkiuat joined
13:25
arkiuat left
13:34
arkiuat joined,
finanalyst left
|
|||
| arkiuat | [Coke] and yes, that's an accurate description of my most recent mistake, but I think I've got things set up properly now | 13:57 | |
| I just yesterday discovered github.com/Raku/doc/milestones | 14:05 | ||
| I guess this hasn't been updated recently, but it's useful to have a distinction drawn between milestone issues and backlog issues | |||
|
16:52
finanalyst joined
|
|||
| arkiuat | the very first code example in the section docs.raku.org/type/Junction#Failur...exceptions actually fails for me when I run it, although the documentation there says that it won't fail | 18:17 | |
| lizmat | yeah, that example is bogus | 18:55 | |
| completely bogus | |||
| if assumes that you can iterate over the eigenstates of a Junction: well, you can't | 18:56 | ||
| "That is what we do in the loop that runs over the elements of the junction, adding them to a list only if they are defined." is bogus | 18:58 | ||
| arkiuat [Coke] ^^ | |||
| fwiw, that's why I made raku.land/zef:lizmat/eigenstates | 18:59 | ||
| arkiuat | lizmat, thanks! I guess we should rewrite that part of the doc then | 19:16 | |
| lizmat | I was thinking about an alternative, but sadly it's pretty hard | 19:21 | |
| all I could come up with is: | |||
| m: my $j = +any "not a number", "42", "2.1"; say $j ~~ Failure | |||
| camelia | True | ||
| arkiuat | well, that's better than having confidently stated falsehoods in the docs | 19:23 | |
| especially when we're talking about Junctions, which are already confusing enough to most people without this kind of shenanigans | 19:27 | ||
| yeah, I see github.com/Raku/doc/issues/3030 was opened for this exact section of the doc (but with an earlier version of this example) in 2019, and JJ wrote this new version (which apparently worked back then?) in response. But now JJ's version is failing. Huh. | 19:33 | ||
| lizmat | I think Junctions iterated before Xmas (as in before 6.c was released in 2015)... so not sure what was going on here | 19:34 | |
| arkiuat | I left a comment on issue #3030 suggesting either reopening it or making a new issue. JJ seemed to think this all had something to do with AUTOTHREAD, as he opened an issue to document it better (mentioning #3030), and the one is stil open | 19:40 | |
| s/the/that/ | |||
| lizmat | Ah... ok hmmm | 19:50 | |
| m: my $j = +any "not a number", "42", "2.1"; sub check($_} { say "Failure" when Failure }; check $j | 19:51 | ||
| camelia | ===SORRY!=== Error while compiling <tmp> Malformed parameter at <tmp>:1 ------> not a number", "42", "2.1"; sub check($_<HERE>} { say "Failure" when Failure }; check expecting any of: constraint |
||
| lizmat | meh | ||
| yeah, that's not going to work, as the Failure will fire if passed as an argument | 19:52 | ||
|
20:06
arkiuat left
|
|||
| [Coke] | milestones date from when I was much more ambituous about getting things done | 20:08 | |
| but yes, if you focus on things with a milestone, that's probably better than things in the backlog bucket. | 20:09 | ||
| ... but on the gripping hand, a ticket closed is a ticket I don't need to worry about | |||
|
20:24
arkiuat joined
20:28
arkiuat left
20:31
disbot5 joined
20:33
coleman_ joined
20:35
arkiuat joined
20:40
arkiuat left
20:41
disbot4 left,
coleman left,
coleman_ is now known as coleman
21:02
arkiuat joined
21:07
arkiuat left
21:20
arkiuat joined
|
|||
| timo | m: my $j = +any "not a number", "42", "2.1"; sub check(Any $_) { say "Failure" when Failure }; check $j | 21:29 | |
| camelia | Failure | ||
| timo | the failure does not fire when passing it | ||
|
21:44
arkiuat left
22:01
arkiuat joined
22:10
arkiuat left
22:23
arkiuat joined
|
|||
| arkiuat | timo, do you think your snippet would make a good replacement for that code sample in the docs? | 22:26 | |
| [Coke], gotcha. I was pleased to see that #3881 was in the milestone bucket and not the backlog one | |||
| timo | hm, no don't think it should go in the docs | 22:49 | |
| i merely wanted to correct lizmat's last eval | |||
| [Coke] | I went through the list, made two new milestones (one for end of year, one for 2026-Q1), and moved some stuff around | 22:54 | |
| (and kept that one in the current bucket!) | 22:56 | ||
| er, the bucket that is current, not the previous old bucket. :) | |||
| lizmat | m: my $j = +any "not a number", "42", "2.1"; sub check($value) { say "Failure" if $value ~~ Failure }; check $j # looks like $_ is default Mu, using any other variable also works | 23:29 | |
| camelia | Failure | ||