🦋 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: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm Set by lizmat on 8 June 2022. |
|||
00:00
reportable6 left
00:03
reportable6 joined
01:17
squashable6 left
01:19
squashable6 joined
|
|||
MasterDuke | jdv++ | 01:33 | |
04:05
kjp left
04:08
kjp joined,
kjp left,
kjp joined
05:28
Xliff left
06:00
reportable6 left
06:03
reportable6 joined
07:20
squashable6 left
07:21
squashable6 joined
07:30
kurahaupo left,
kurahaupo joined
08:32
sena_kun joined
09:08
nine left,
nine joined
11:52
guifa left
11:53
guifa joined
11:54
guifa joined
12:00
reportable6 left
12:03
reportable6 joined
13:33
ab5tract joined
16:54
ab5tract left
|
|||
lizmat | m: say Q|foo(42)|.AST | 17:13 | |
camelia | ===SORRY!=== Error while compiling Undeclared routine: foo used at line -1. Did you mean ''? |
||
lizmat | nine: ^^ I'd say that is wrong, it should complain at EVAL time if there is truly no sub found | 17:14 | |
17:54
linkable6 left,
evalable6 left
17:55
linkable6 joined
17:57
evalable6 joined
18:00
reportable6 left
18:03
reportable6 joined
|
|||
patrickb | I have just uploaded the binary release archives for 2023.06 to rakudo.org. Yay! | 18:18 | |
lizmat | patrickb++ | 18:20 | |
nine | m: foo(42) | 19:16 | |
camelia | ===SORRY!=== Error while compiling <tmp> Undeclared routine: foo used at line 1 |
||
nine | lizmat: that's just the same. Subroutine calls are resolved at compile time and we complain if we can't do that. | ||
lizmat | I guess we then need some post CHECK time or something like that | 19:17 | |
because I could be building an AST with the .AST function, which references foo | 19:18 | ||
and then later combine that AST with another AST that *does* contain the "foo" sub | |||
that currently doesn't work :-( and makes Formatter more convoluted atm | 19:20 | ||
so it feels to me we need a AST CHECK time functionality, and an EVAL CHECK time functionality | |||
I mean, we should see RakuAST as building blocks, no? | 19:22 | ||
nine | Sure, RakuAST nodes are building blocks. .AST is a debugging aid | 19:25 | |
lizmat | well, I'm at a bit of a conundrum re q:o/%s/ being compile time then | 19:29 | |
in the current code, this references some helper subs that are in scope | |||
however, they do not get properly QASTed, or maybe bytecoded, probably because these subs are not in the sc | 19:30 | ||
so I'm not adding the ASTs of these subs to the generated AST, and those ASTs are generated from the code of the original subs using .AST | 19:32 | ||
this for maintenance / development convenience | |||
nine | So....there is some bug and you are trying to work around that but that is tedious so you use a debugging aid that was never meant for such a thing and it doesn't work out well? | 19:42 | |
lizmat | from a conversation with jnthn I gathered that it would be hard to fix, these missing subs | 19:45 | |
nine | When has that ever kept us from fixing things? :D | 19:46 | |
Well, except for the still existing race condition in MoarVM's expression JIT compiler... | |||
lizmat | ok, let's see if I can golf it | ||
nine; golfed gist.github.com/lizmat/91930d595ca...9953a8f26a | 19:58 | ||
afk for a bit& | 20:05 | ||
20:15
[Coke] left
20:23
[Coke] joined
20:28
[Coke] left
20:48
[Coke] joined
21:58
sourceable6 left,
nativecallable6 left,
benchable6 left,
linkable6 left,
committable6 left,
notable6 left,
squashable6 left,
releasable6 left,
bloatable6 left,
statisfiable6 left,
reportable6 left,
quotable6 left,
coverable6 left,
bisectable6 left,
tellable6 left,
greppable6 left,
unicodable6 left,
evalable6 left,
shareable6 left
21:59
notable6 joined,
benchable6 joined,
squashable6 joined,
bloatable6 joined,
bisectable6 joined,
coverable6 joined,
reportable6 joined
22:00
unicodable6 joined,
linkable6 joined,
committable6 joined
22:01
shareable6 joined,
greppable6 joined,
releasable6 joined,
statisfiable6 joined,
sourceable6 joined,
evalable6 joined,
quotable6 joined,
nativecallable6 joined,
tellable6 joined
22:09
sena_kun left
22:20
tonyo left,
tonyo joined
|
|||
timo | nine: why is there a race condition in the exprjit compiler, we never run more than one thread that does speshing and jitting | 22:40 | |
22:49
[Tux] left
23:01
[Tux] joined
|
|||
ugexe | github.com/rakudo/rakudo/blob/ec62...y.pm6#L178 Shouldn't this read be protected? | 23:45 | |
yep, it was broken in github.com/rakudo/rakudo/commit/95...03b53597ba | 23:48 | ||
the Lock::Soft code was eventually reverted but the original protected block wasn't returned |