00:44
Sgeo joined
01:02
hudo left
01:03
hudo joined,
hudo left
01:04
hudo joined
01:09
Manifest0 left
02:58
hulk joined
02:59
kylese left
03:02
nil78 left
03:06
wbooze joined
03:12
nil78 joined
03:15
hulk left,
kylese joined
04:13
Aedil joined
04:21
Aedil left
04:26
Aedil joined
04:27
jpn joined
04:32
jpn left
04:34
topnep left
04:35
topnep joined
06:17
nil78 left,
nil78 joined
06:39
topnep left
06:40
topnep joined
06:44
jpn joined
06:49
jpn left
06:54
jpn joined
06:58
jpn left
07:13
Sgeo left
07:19
nil78 left
07:21
silug left
07:40
nil78 joined
07:49
jpn joined
08:09
jpn left
08:12
jpn joined
08:26
jpn left
08:44
topnep left,
topnep joined
08:46
jpn joined
08:52
jpn left
08:56
wayland76 joined
09:11
dakkar joined
|
|||
wayland76 | Where do I send PRs for community modules (like github.com/raku-community-modules/XML/pull/71 ) so that they get some attention? | 09:18 | |
(Hi again :) ) | |||
If anyone is interested, I added "does Positional" and the tests ran fine, but when I tried adding "does Associative", they almost all failed, even though the class in question already has an AT-KEY method. | 09:19 | ||
lizmat | wayland76: there's a #raku-community-modules channel where you can ask questions like these | 09:24 | |
which also is where Geth posts updates | 09:25 | ||
wayland76 | Lovely! Thanks! | 09:28 | |
09:32
jpn joined
09:39
gfldex left
09:40
gfldex joined
09:45
nil78 left
09:47
nil78 joined
09:58
sena_kun joined
10:00
euandreh left,
euandreh joined
|
|||
wayland76 | Hi! Just spotted ≽ on the Raku Operators page, but with no description. Does anyone know what it's for? | 10:38 | |
10:48
topnep left
10:50
topnep joined
11:03
thundergnat joined
|
|||
thundergnat | wayland76: ≽ is a deprecated operator. It used to mean "is a super set of" or "contains". | 11:04 | |
m: say <v g> ≽ 'g'; | |||
camelia | ≽ was removed in v6.d, please use ⊇ operator instead or compile your code with 'use v6.c' in block <unit> at <tmp> line 1 |
||
thundergnat | m: say <v g> ⊇ 'g'; | ||
camelia | True | ||
11:16
lizmat left,
lizmat_ left,
lizmat joined
11:26
Altai-man joined
11:29
sena_kun left
11:39
nil78 left
11:41
nil78 joined
11:56
wbooze_ joined
11:58
Manifest0 joined
11:59
wbooze is now known as Guest5774,
Guest5774 left,
wbooze_ is now known as wbooze
12:01
Geth joined
12:54
topnep left
12:55
topnep joined
13:00
nil78 left
13:03
nil78 joined
13:12
jpn left
13:13
nil78_ joined,
nil78 left
13:29
wbooze left
13:53
jpn joined
13:58
jpn left
14:10
jpn joined
14:37
wbooze joined
14:59
topnep left
15:00
apac joined
15:03
topnep joined
|
|||
librasteve | timo: I would be happy to f/back on the bikeshedding - looks like tbrowder is going to resubmit a new PR with changes so far | 15:11 | |
tbrowder: please can you put a link here to the new PR when it's ready so that I can tear it to shreds ;-) | 15:12 | ||
btw I have checked that yoou can enter the literal unicode char into the docs search 🐧and it will get correctly pushed up to google search and back down to a valid result list | 15:14 | ||
15:15
librasteve_ joined
|
|||
wayland76: would you be kind enough to raise an issue (ideally a PR) to remove the deprecated operator (or maybe better to describe it's status) | 15:18 | ||
15:20
nil78_ left
|
|||
wayland76: I went through a lot of trial and error with Positional and Associative to make a DataFrame in the Dan module you are welcome to review what I settled on github.com/librasteve/raku-Dan/blo...kumod#L794 | 15:21 | ||
the idea was to implement cascading accessors like say df[0][0];, say df[0]<A>;,say df{"2022-01-03"}[1]; and so on | 15:24 | ||
15:24
nil78 joined
|
|||
I ended up with role DataFrame does Positional does Iterable {} so chose to implement the Associative aspects with custom postcircumfix instead of AT-KEY | 15:26 | ||
15:29
Aedil left
|
|||
timo | please be aware that operators are part of the language, in other words lexically scoped. if you put the object in any code that tries to use postcircumfix:<{ }> on it, it will use the core version, not your custom one | 15:48 | |
you might also be interested in `has @!data handles <iterator flat lazy hyper Numeric list>;` | 15:53 | ||
15:54
Aedil joined
15:55
Sgeo joined
16:01
Aedil left
|
|||
librasteve | timo: good point - it works for my case, since my class specifically does NOT claim is Associative or similar | 16:04 | |
nor does it have an AT-KEY method | |||
16:06
Aedil joined
16:10
Sgeo left
16:13
Sgeo joined
|
|||
melezhik. | Good news. Today I have had a meeting with RockyLinux QA team , the agreed to give it Sparrow a try … I do some prototyping this and next week. So fingers crossed 🤞) | 17:05 | |
17:07
topnep left
17:08
topnep joined
17:32
wbooze left
17:38
dakkar left
17:53
wbooze joined
18:01
lichtkind joined
18:33
apac left
18:37
eseyman left
18:39
manu_ joined
18:40
manu_ is now known as eseyman
18:41
wbooze left
18:51
jpn left
19:12
topnep left
19:13
apac joined,
topnep joined
19:17
nil78 left
19:20
nil78 joined
19:27
wayland joined,
wayland76 left
|
|||
lizmat | 🤞 !! | 19:46 | |
20:07
Aedil left
20:31
nil78 left
20:43
nil78 joined
20:46
jpn joined
21:05
jpn left
21:15
Altai-man left
21:16
Altai-man joined
|
|||
wayland | librasteve: Thanks! Regarding Positional and Associative, I did the same with TOP, though I relied heavily on Hash::Agnostic and Array::Agnostic (after appropriate bugfixes). The Positional stuff on XML was an easy fix; Associative will be harder, but I think it'll just be a matter of reading the docs and looking for other functions to implement or something. | 21:16 | |
21:16
topnep left
|
|||
wayland | melezhik: Good news :) | 21:17 | |
21:17
topnep joined
|
|||
tbrowder | librasteve_: you’ll normally see those links automagically on #raku-doc | 21:18 | |
wayland | librasteve: PR done :) | 21:33 | |
21:52
jpn joined
22:00
jpn left
22:05
yewscion joined
22:12
jpn joined
22:14
yewscion left
22:17
jpn left
22:29
jpn joined
22:30
lichtkind left
22:33
jpn left
22:44
Altai-man left,
wayland left
22:47
jpn joined
22:52
jpn left
23:11
apac left
23:21
topnep left
23:24
topnep joined
23:41
jpn joined
23:47
SrainUser joined
|
|||
SrainUser | Parallelism with "start" in for loops seem unreliable. When I run: | 23:49 | |
for 1..5 { | 23:50 | ||
start { | |||
say "hi"; | |||
} | |||
} | |||
evalable6 | hi | ||
SrainUser | I get different amounts printed with each run. Is this normal? | ||
23:51
jpn left
|