|
🦋 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: ... | log inspection situation still under development | For MoarVM see #moarvm Set by lizmat on 22 May 2021. |
|||
|
00:03
reportable6 left
00:05
reportable6 joined
|
|||
| [Coke] | MasterDuke++ nine++ | 00:30 | |
|
02:20
rouking left
04:35
samcv_ joined
04:37
quotable6 left,
linkable6 left,
notable6 left,
committable6 left,
shareable6 left,
benchable6 left,
releasable6 left,
reportable6 left,
unicodable6 left,
jjatria left,
bartolin left,
samcv left,
squashable6 left,
sivoais left,
MasterDuke left,
squashable6 joined
04:38
sivoais joined,
bartolin joined
04:39
jjatria joined,
benchable6 joined
04:40
reportable6 joined,
quotable6 joined
04:41
shareable6 joined,
releasable6 joined,
notable6 joined
04:42
committable6 joined,
linkable6 joined,
unicodable6 joined
05:22
squashable6 left
05:23
frost joined
05:25
squashable6 joined
06:02
reportable6 left
06:05
reportable6 joined
06:36
Kaiepi left,
japhb left,
LizBot left,
moon-child left,
SmokeMachine left,
cognominal left,
leont left,
JRaspass left
06:37
Kaiepi joined,
japhb joined,
LizBot joined,
moon-child joined,
SmokeMachine joined,
cognominal joined,
leont joined,
JRaspass joined
|
|||
| japhb | Anyone know how often raku.land and modules.raku.org update? | 07:28 | |
| tellable6 | 2021-06-05T17:13:48Z #raku <holly> japhb : thanks, I joined :-) | ||
| japhb | After uploading to fez and doing `zef update`, my uploads are visible via `zef info` pretty quickly, but it's not clear what the expected delay is for the websites. | 07:29 | |
| raydiak | if the readme is still accurate, an update is started on the 20th and 50th minutes of every hour. the last 2 update logs seemed to coroborate this. the most recent update took about 22 minutes and completed at 8:12 UTC (10 minutes ago) | 08:22 | |
| that's for modules.raku.org | 08:23 | ||
| I don't pay much attention to raku.land because it doesn't index version * modules (all of my modules). but according to gitlab.com/raku-land/raku-land/-/jobs it runs every 3 hours, about 5ish minutes after the start of hours which are integer multiples of 3, and takes less than 3 minutes to complete | 08:31 | ||
| japhb | Thank you, raydiak. Seems like raku.land could probably update a lot more often (as often as modules.raku.org, for instance). | 09:08 | |
| raydiak | happy to help. maybe it's a restriction of gitlab...looks like free accounts only get 400 ci/cd minutes per month. by those numbers it's already exceeding that, so JRaspass++ is already being forced into paying for it, and maybe spending his minutes on other projects as well | 09:15 | |
| Geth | ¦ problem-solving: JJ assigned to codesections Issue There should be a (relatively easy) way to specify how to test for non-Raku dependencies github.com/Raku/problem-solving/issues/283 | 09:20 | |
| nine | raydiak: why don't you give your modules proper versions? | 09:27 | |
| japhb | raydiak: Ooof, yeah, having to pay extra would hurt. | 09:35 | |
| raydiak | nine: a few reasons, basically all just a mix of historical baggage, stubborn opinionatedness, laziness, and indecision. they were all written at a time when that was a more common and accepted practice, didn't matter to the ecosystem or old tools. none of them were ever really done enough to be considered even in beta, so I regarded versioning as largely pointless. my work on them moved in highly variable | 09:40 | |
| patterns that didn't necessarily lend themselves well to clear separation between one version and the next. I don't like the maintenance aspect of having to update the number or complicate my process with some tool to handle it for me. I don't like the muddling of api version and version version we have now. and at this point I haven't decided whether I'm going to develop them, maintain them, or abandon | |||
| them | |||
| understand, I don't regard most of that as valid and reasonable decision-making process. it's just the truth | 09:41 | ||
|
11:43
committable6 left,
nativecallable6 left,
benchable6 left,
releasable6 left,
unicodable6 left,
coverable6 left,
evalable6 left,
greppable6 left,
sourceable6 left,
notable6 left,
linkable6 left,
reportable6 left,
bloatable6 left,
statisfiable6 left,
tellable6 left,
bisectable6 left,
quotable6 left,
shareable6 left,
squashable6 left
11:44
linkable6 joined,
shareable6 joined,
releasable6 joined,
squashable6 joined,
sourceable6 joined
11:45
bisectable6 joined,
benchable6 joined,
nativecallable6 joined,
reportable6 joined,
bloatable6 joined,
notable6 joined,
greppable6 joined,
evalable6 joined,
quotable6 joined
11:46
tellable6 joined,
unicodable6 joined,
coverable6 joined,
committable6 joined
11:47
statisfiable6 joined
12:02
reportable6 left
12:06
reportable6 joined
13:40
MasterDuke joined
13:50
squashable6 left
13:51
squashable6 joined
17:26
RakuIRCLogger left,
LizBot left,
lizmat_ joined
17:27
LizBot joined,
RakuIRCLogger joined
17:28
lizmat left
17:29
lizmat_ is now known as lizmar,
lizmar is now known as lizmat,
lizmat left,
lizmat joined
18:02
reportable6 left
18:05
reportable6 joined
18:08
notna joined
19:07
notna left
19:56
Xliff joined,
dogbert11 joined
|
|||
| Xliff | I'm trying to learn some of RakuAST. Can anyone involved tell me where the best place is to look for all nodes involved in method creation? | 19:56 | |
| Thanks. | |||
|
19:59
dogbert17 left
|
|||
| raydiak | looks like method nodes are defined in github.com/rakudo/rakudo/blob/raku...de.rakumod | 20:44 | |
| MasterDuke | Xliff: you might be interested in github.com/rakudo/rakudo/tree/spee...call_setup and github.com/MoarVM/MoarVM/tree/set_...ialization | 21:01 | |
| not related to rakuast, but for nativecall compilation speedups | |||
| Xliff | Masterduke++ # Thanks!\ | 21:47 | |
| gist.github.com/Xliff/edd9b31e11a8...a5c4b76cbf | 22:21 | ||
| ^^ jnthn timotimo lizmat | 22:22 | ||
| japhb | It looks like there are some bugs in there. Freehanded? | 22:23 | |
| Also, I think it's just 'timo' here on Libera.Chat | 22:28 | ||
| raydiak | some bugs? either I'm really confused about what I'm reading in rakuast, or the whole thing is imagined...maybe intended as pseudocode or something? | 22:53 | |
| Xliff | japhb: Yeah, freehanded pseudocode. | 22:55 | |
| Bugs? Pleae eludiate. | |||
| Wording updated for clarity. # ( | 22:57 | ||
| (radiak, japhb)».++ | 23:00 | ||
| # (No that is not valid...) | |||
| raydiak | by bugs I think he just meant it won't run. but if you intended it as pseudocode, that explains it. from my understanding, that's somewhat like what it'll look like, yes. just the node names are mostly different and arranged a little differently in places, constructor parameters are named instead of positional unless there's only one of them, stuff like that. but you do have the general idea in a very | ||
| high-level sense, yes | |||
| Xliff | Thanks! | 23:01 | |
| I just don't know where to find the actual nodes in the source to get everything correct. | |||
| raydiak | you're welcome | ||
| I don't think there's a document listing them yet, but theyu're all defined in github.com/rakudo/rakudo/tree/raku...c/Raku/ast | 23:02 | ||
| Xliff | Yeah, but I have no idea where to start. I think I'll look into the tests, for now,. | ||
| raydiak | it's not too hard to read. methods and subs and blocks and such are in code.rakumod, variable decls are in variable-declaration, variable access in variable-access, method/sub calls are in call, etc. reading the tests is a good idea, I haven't even looked at those yet | 23:05 | |
| Xliff | Thanks for that! | ||
| raydiak | sure thing, yw | 23:06 | |