|
🦋 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:01
reportable6 joined
03:27
quotable6 left,
committable6 left,
unicodable6 left,
greppable6 left,
sourceable6 left,
linkable6 left,
evalable6 left,
greppable6 joined,
committable6 joined
03:28
sourceable6 joined,
unicodable6 joined
03:29
evalable6 joined,
quotable6 joined,
linkable6 joined
04:26
epony left
05:26
bloatable6 left,
sourceable6 left,
linkable6 left,
evalable6 left,
notable6 left,
tellable6 left,
coverable6 left,
nativecallable6 left,
committable6 left,
statisfiable6 left,
bisectable6 left,
shareable6 left,
unicodable6 left,
greppable6 left,
reportable6 left,
squashable6 left,
releasable6 left,
benchable6 left
05:27
greppable6 joined,
benchable6 joined,
reportable6 joined,
notable6 joined,
linkable6 joined,
unicodable6 joined
05:28
nativecallable6 joined,
squashable6 joined,
bisectable6 joined,
shareable6 joined,
sourceable6 joined,
tellable6 joined,
committable6 joined,
statisfiable6 joined
05:29
releasable6 joined,
coverable6 joined,
bloatable6 joined,
evalable6 joined
06:00
reportable6 left
06:01
reportable6 joined
|
|||||||||||||||||||||||||||||||||||||||
| [Tux] | Rakudo v2022.12-1-gd52342eb0 (v6.d) on MoarVM 2023.02-3-g6adfc376c
|
06:38 | |||||||||||||||||||||||||||||||||||||
|
07:39
sena_kun joined
08:43
squashable6 left
08:46
squashable6 joined
10:50
epony joined
12:00
reportable6 left
12:02
reportable6 joined
|
|||||||||||||||||||||||||||||||||||||||
| [Coke] | tux - why is rakudo still reporting as v2022? | 12:24 | |||||||||||||||||||||||||||||||||||||
| (master/main switch not tracked, maybe?) | |||||||||||||||||||||||||||||||||||||||
| [Tux], I mean. | 12:25 | ||||||||||||||||||||||||||||||||||||||
| [Tux] | possible. I'll have a look | 12:42 | |||||||||||||||||||||||||||||||||||||
|
12:43
Altai-man joined,
sena_kun left
|
|||||||||||||||||||||||||||||||||||||||
| [Tux] | indeed, all is master, not main. | 13:19 | |||||||||||||||||||||||||||||||||||||
| lizmat | time to change :-) | 13:20 | |||||||||||||||||||||||||||||||||||||
| at least the Rakudo branch | |||||||||||||||||||||||||||||||||||||||
| [Tux] | my script updates git using "master" everywhere", so lets see where stuff starts breaking when I switch to "main" | 13:22 | |||||||||||||||||||||||||||||||||||||
| lizmat | I think MoarVM is still on master | ||||||||||||||||||||||||||||||||||||||
| but nqp and rakudo are on main | 13:23 | ||||||||||||||||||||||||||||||||||||||
| [Tux] | time to change :) | ||||||||||||||||||||||||||||||||||||||
Rakudo v2023.02-291-ge68322dbc (v6.d) on MoarVM 2023.02-3-g6adfc376c
|
13:38 | ||||||||||||||||||||||||||||||||||||||
| [Coke] | ok, but the numbers went in the wrong direction. :) | ||||||||||||||||||||||||||||||||||||||
| [Tux] | yes, but it could be that this is during "normal" hours and my box is also used for other tasks | 13:40 | |||||||||||||||||||||||||||||||||||||
| lizmat | I think those increased numbers are mainly additional startup from loading all of the RakuAST stuff | ||||||||||||||||||||||||||||||||||||||
| and the additional grammar / actions | |||||||||||||||||||||||||||||||||||||||
| [Tux] | anyway, well-noticed! | ||||||||||||||||||||||||||||||||||||||
| [Coke] | \o/ | 13:42 | |||||||||||||||||||||||||||||||||||||
| lizmat | hmmm... it just occurred to me we could potentially have a simplified Rakudoc grammar that would just produce an AST | 14:29 | |||||||||||||||||||||||||||||||||||||
| which *could* be the base of translators | |||||||||||||||||||||||||||||||||||||||
| building the AST for a .rakudoc file would then be: slurp($file).AST(DocGrammar) | 14:30 | ||||||||||||||||||||||||||||||||||||||
| or something similar | 14:31 | ||||||||||||||||||||||||||||||||||||||
| nine | Wouldn't that have to parse full Raku to even find all the Rakudoc? | 14:32 | |||||||||||||||||||||||||||||||||||||
| lizmat | not if we consider the code an Doc::Ambient | ||||||||||||||||||||||||||||||||||||||
| as per S26 | |||||||||||||||||||||||||||||||||||||||
| meanwhile, I just found out that Block and PointyBlock are also DeclaratorTargets :-( | 14:33 | ||||||||||||||||||||||||||||||||||||||
| nine | That just says what could happen to source code. But how do you differentiate between POD and Raku mixed in the same file without actually understanding the Raku? What looks like POD could be part of a string for example. | 15:05 | |||||||||||||||||||||||||||||||||||||
| lizmat | true | 15:06 | |||||||||||||||||||||||||||||||||||||
| still, I think for pure .rakudoc files, it would be helpful? | |||||||||||||||||||||||||||||||||||||||
| and safer, as no code can run ? | 15:07 | ||||||||||||||||||||||||||||||||||||||
|
16:15
Altai-man left
16:17
sena_kun joined
16:41
sena_kun left,
sena_kun joined
|
|||||||||||||||||||||||||||||||||||||||
| Geth | rakudo/main: 5566049023 | (Stefan Seifert)++ | 2 files RakuAST: first support for Perl 5 regex dialect |
17:45 | |||||||||||||||||||||||||||||||||||||
| nine | Another one of those unexpected wins | 17:46 | |||||||||||||||||||||||||||||||||||||
| [Coke] | (rakudoc) - I would be fine if raku foo.rakudoc implied --doc | 17:58 | |||||||||||||||||||||||||||||||||||||
| it is a little suprising that .rakudoc implies nothing other than .raku | 17:59 | ||||||||||||||||||||||||||||||||||||||
|
18:00
reportable6 left
18:01
reportable6 joined
|
|||||||||||||||||||||||||||||||||||||||
| lizmat | [Coke]: I think some @ARGS twiddling in src/main.nqp just before $comp.command_line, would do the trick | 18:05 | |||||||||||||||||||||||||||||||||||||
|
19:01
sena_kun left
19:04
sena_kun joined
|
|||||||||||||||||||||||||||||||||||||||
| Geth | rakudo/main: d9dd95c1dd | (Elizabeth Mattijsen)++ | 12 files RakuAST: complete grammar support for declarator docs Trailing declarator docs can now only be specified if they start on the same line as the declarand they refer to. This is a much saner approach than in the legacy grammar where it was quite uncertain where (if ever) trailing declarator docs would get attached to. ... (19 more lines) |
19:11 | |||||||||||||||||||||||||||||||||||||
| lizmat | *phew* that took a *lot* of iterations | ||||||||||||||||||||||||||||||||||||||
| 771! | 19:17 | ||||||||||||||||||||||||||||||||||||||
| [Coke] | 771 is a lot of iterations! | 19:40 | |||||||||||||||||||||||||||||||||||||
| nine | Shouldn't this test actually fail? github.com/rakudo/rakudo/blob/main...ity.t#L121 | 19:45 | |||||||||||||||||||||||||||||||||||||
| It declares an our scoped class A while there already is a class by that name in the outer scope | 19:46 | ||||||||||||||||||||||||||||||||||||||
|
20:04
evalable6 left,
linkable6 left,
linkable6 joined
20:05
evalable6 joined
20:51
squashable6 left
20:53
squashable6 joined
21:41
sena_kun left
|
|||||||||||||||||||||||||||||||||||||||
| Geth | rakudo/main: ae0c69a935 | (Elizabeth Mattijsen)++ | 5 files RakuAST: add .raku / deparsing / tests for RakUAST::Statement::Need Sadly, we need to make "import" work as well to really test it. |
22:14 | |||||||||||||||||||||||||||||||||||||
| rakudo/main: 01abff7599 | (Elizabeth Mattijsen)++ | 3 files RakuAST: add missing parts for doc declarators on ::(Pointy)Block So that declarator docs now also work on (pointy) blocks |
22:41 | ||||||||||||||||||||||||||||||||||||||
|
23:25
evalable6 left,
linkable6 left
23:26
evalable6 joined
23:27
linkable6 joined
|
|||||||||||||||||||||||||||||||||||||||