|
01:29
Aedil joined
02:08
hulk joined
02:09
kylese left
03:15
hulk left,
kylese joined
03:30
kylese left
03:35
kylese joined
04:17
hudo_ left
04:18
hudo_ joined
07:22
skyesoss joined
07:23
skyesoss left
07:25
skyesoss joined
07:27
skyesoss_ joined
07:28
skyesoss left
07:34
Sgeo_ joined
07:38
Sgeo left
08:09
Xliff joined
|
|||
| Xliff | \o | 08:09 | |
| Is there a way to get raku to list its infix ops? | |||
| m: say &infix:<+> | |||
| camelia | &infix:<+> | ||
| Xliff | Oh! CORE!~ | 08:12 | |
| m: CORE::.keys.grep({ .starts-with("\&infix") }).gist.say | 08:14 | ||
| camelia | (&infix:<gt> &infix:«<=>» &infix:<^…^> &infix:<unicmp> &infix:<≤> &infix:</> &infix:«>=» &infix:<and> &infix:<≠> &infix:<⚛=> &infix:<⩵> &infix:<before> &infix:<^..^> &infix:«(>=)» &infix:<**> &infix:<÷> &infix:<!~~> &infix:<⊎> &infi… | ||
|
08:22
Xliff left
08:43
skyesoss_ left
|
|||
| antononcube | @ab5tract Brian Duggan figured out a (short) workaround, see : github.com/bduggan/raku-jupyter-ke...issues/115 | 08:50 | |
| @ab5tract I also successfully tried out the Rakudo-HEAD Docker file you provided -- thanks! | 09:13 | ||
| librasteve | wonders do these docker images get posted to hub.docker.com or similar? | 09:34 | |
| antononcube | The one I referred to seems experimental -- I think @ab5tract made a change in Rakudo in order to make the chatbook evaluations work. | 09:38 | |
|
09:47
finanalyst joined
09:49
Aedil left
10:02
Aedil joined
10:04
Aedil left,
Aedil joined
10:17
Sgeo_ left
|
|||
| finanalyst | .tell [Coke] there is a rendered version of RakuDoc v2 at raku.github.io/rakudoc I'm putting up a PR with a link to it in the raku.docs/language/pod file | 11:06 | |
| ab5tract | I created a Dockerfile based on debian:latest that builds its own rakudo | 11:14 | |
| I’m not sure of any docker base images that track rakudo head. There used to be rakudo:daily but it was still using a 2023 build when I checked | 11:15 | ||
| lizmat | wouldn't that mean that every CI run with that image would rebuild Rakudo from scratch ? | 11:16 | |
| ab5tract | Only if you set the image to be built by CI | ||
| lizmat | what happens if you don't ? | 11:17 | |
| ab5tract | It’s not the default Dockerfile in the project | ||
| It’s just a custom Dockerfile that users can choose to build locally | |||
| The regular Dockerfile in Jupyter-chat book is also not built by CI afaik | 11:18 | ||
| lizmat | so what would be needed to revive a daily build ? | ||
| e.g. I wouldn't mind seeing all of my modules being checked every night with the latest Rakudo | 11:19 | ||
| ab5tract | contact Dr. Suman Khamal I guess? | ||
| lizmat | but I guess I could do that locally hmmmm | ||
| with your Docker file I mean | |||
| ab5tract | You could base such an effort on mine indeed | 11:20 | |
| github.com/antononcube/Raku-Jupyte...akudo-HEAD | |||
| hub.docker.com/r/sumankhanal/rakudo | 11:22 | ||
| Weird that it says updated 5 months ago on docker hub | |||
| guifa | nice. just got a DNS and mDNS packet module done. Probably in the next day or so I'll have a fully functioning ZeroConf service module | 12:54 | |
| (once mods are made in moarvm and rakudo) | 12:57 | ||
| lizmat | guifa++ | 12:59 | |
| guifa | we don't have any way to expose private innards to subclasses right? | 13:03 | |
| outside of trusts | |||
| lizmat | indeed, that's why they're private | 13:04 | |
| I guess the next level would be "implementation-detail" | |||
| * a public method with | |||
| guifa | ah yeah | 13:09 | |
| good point | |||
| I always forget about that trait | |||
| to keep things speedy, all the DNS packets are just being kept as blobs with an offfset | |||
| queries and responses just keep a reference to the same blob, but with a different offset | 13:10 | ||
| there's a method for calculating the name (does a weird format) that doesn't need to be exposed, but an mDNS packet shifts the interpretation a teeny bit (utf8 instead of ascii) | 13:11 | ||
| and of course I over-obsess over these tiny details ^_^ | 13:12 | ||
|
14:00
melezhik joined
|
|||
| melezhik | o/ | 14:01 | |
|
14:02
melezhik left
14:03
finanalyst left
|
|||
| antononcube | I assume it is fine making Raku packages with the Affero GPL3 (AGPL3)? | 14:03 | |
| How can I find / search AGPL3 packages in raku.land? Or anywhere else. | 14:04 | ||
| ab5tract | antononcube: looks like a license filter would be a nice addition to raku.land | 15:19 | |
| when I add a package management UI to Comma, I'll try to remember to add it | 15:20 | ||
| for now, I think your best option is to download the ecosystem and filter the meta files | 15:21 | ||
| antononcube | Right, I have to do that anyway at some point in order to repeat the package recommender exercise. | 15:22 | |
|
15:23
finanalyst joined
15:24
sena_kun left,
guifa left,
sena_kun joined
|
|||
| ab5tract | 360.zef.pm/ <--- this has got the goods :) | 15:25 | |
| and this one too: raw.githubusercontent.com/Raku/REA.../META.json | |||
| also here: raw.githubusercontent.com/ugexe/Pe.../p6c1.json | 15:26 | ||
|
15:28
sena_kun left
15:30
sena_kun joined
15:38
zetaaaa joined
15:52
finanalyst left
|
|||
| ugexe | p6c1.json hasnt been updated in a long time. it shouldnt be used | 15:53 | |
| the REA META.json replaces it | 15:54 | ||
|
15:56
zetaaaa left
15:57
MyNetAz left
16:12
MyNetAz joined
|
|||
| [Coke] | Your own packages can have whatever license you like, I'm sure - if you're asking about raku community, I'd love to get a concensus first. | 16:56 | |
| c: HEAD say 3 | 17:00 | ||
| committable6 | [Coke], ¦HEAD(e5a715a): «3» | ||
|
17:01
melezhik joined
|
|||
| melezhik | Thinking about building micro service framework on top of Sparky - github.com/melezhik/Dormitory | 17:03 | |
|
17:03
melezhik left
20:42
Sgeo joined
21:02
abraxxa-home joined
21:46
Sgeo left,
Sgeo joined
22:33
abraxxa-home left
22:34
sena_kun left
|
|||
| ab5tract | melezhik: cool! | 23:22 | |
| ugexe, thanks for clarification | |||
|
23:58
MyNetAz left
|
|||