🦋 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:02
reportable6 joined
01:02
linkable6 left,
evalable6 left
01:03
linkable6 joined
01:05
evalable6 joined
01:50
frost joined
01:59
frost left
02:55
frost joined
03:06
frost left
04:34
frost joined
04:58
frost left
05:32
frost joined
05:35
frost left
06:00
heartburn left,
reportable6 left,
reportable6 joined,
heartburn joined
07:05
sena_kun joined
09:35
sena_kun left
11:00
MasterDuke left
|
|||
Geth | rakudo/main: cacd8bba93 | (Elizabeth Mattijsen)++ | 4 files RakuAST: add deparsing/.raku/test for RakuAST::Var::Pod::Finish |
11:27 | |
12:00
reportable6 left
12:02
reportable6 joined
|
|||
lizmat | notable6: weekly | 12:09 | |
notable6 | lizmat, No notes for “weekly” | ||
lizmat | nine: re irclogs.raku.org/raku-dev/2023-03-13.html#07:35 is there a bit of a plan already? | 13:30 | |
would we need to create something like a PodTarget class to hang inline pod off from? | 13:31 | ||
nine | No plan yet | 13:37 | |
lizmat | ok well, that's easy then :-) | 13:40 | |
I guess I will have to familiarize myself with more rakudoc innards then :-) | 13:42 | ||
Q: shouldn't we call the RakuAST classes something with Rakudoc or just Doc instead of Pod ? | |||
nine | Well "pod" is quite well entrenched, e.g. $=pod or even =pod | 13:43 | |
lizmat | well, yes, but do we need to entrench this even further ? | 13:46 | |
nine | Why not? What's there to be gained by changing the name? | 13:49 | |
vrurg | If we don't plan to rename POD then why creating extra confusion? | 13:50 | |
lizmat | but that's just the point: in the Raku documentation, pod files now have the .rakudoc extensions | 13:51 | |
vrurg | Extensions, not the concept/term itself. | ||
lizmat | I think the documentation team has different ideas about it, long term | 13:53 | |
[Coke] ^^ | |||
and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2023/03/27/2023-13-finitely/ | 13:58 | ||
14:38
linkable6 left,
evalable6 left
14:41
linkable6 joined,
evalable6 joined
|
|||
lizmat | ok, pod it is :-) | 15:13 | |
I think I'm going to start by adding some .raku methods to classes in src/core.c/Pod.pm6 | 15:29 | ||
to be able to better understand how these classes are built | 15:30 | ||
nine | That's so.....sensible. Why do you want to make your life so easy? | 15:45 | |
lizmat | heh... turns out I only needed to remove some BUILD methods and make some attributes public | 15:51 | |
also: can someone explain to me why Pod::Block::Declarator is a Pod::Block ?? | 15:52 | ||
I don't see any syntax for giving it any config or contents ? | |||
15:54
japhb left
15:56
japhb joined
|
|||
nine does not have the slightest idea about any Pod related stuff at all... | 16:04 | ||
lizmat neither | |||
Geth | rakudo/main: 1a86348a28 | (Elizabeth Mattijsen)++ | src/core.c/Pod.pm6 Remove some unnecessary BUILD methods And make some attributes public, so .raku will see them. |
16:12 | |
rakudo/main: cd3c58573a | (Elizabeth Mattijsen)++ | src/core.c/Pod.pm6 Streamline Pod::Block classes a bit - complete signature - use pointy block binding where possible - use ternaries where possible - move coercion into signature |
16:50 | ||
[Coke] | (pod vs. rakudoc) I don't care, I'm just trying to track what the core team does. | 16:57 | |
rakudoc was listed as the preferred version ages ago, we finally got around to updating the raku/doc infra to deal with it | |||
17:19
ab5tract joined
|
|||
tonyo | how does rakudoc work? after a fresh install `rakudoc IO::Path.add` shows nothing (even after `rakudoc -b`) | 17:56 | |
Geth | rakudo/main: 3080103bb6 | (Elizabeth Mattijsen)++ | 3 files RakuAST: add stubs for pod handling - RakuAST::Pod, RakuAST::Pod::Block, RakuAST::Pod::Declarator - Some streamlining in RakuAST::CompUnit |
18:00 | |
18:00
reportable6 left
18:01
reportable6 joined
18:22
sena_kun joined
|
|||
[Coke] | tonyo: github.com/Raku/rakudoc/issues/25 | 18:40 | |
tonyo: interestingly, this seems to work with the test data in the rakudoc repo. | 19:10 | ||
RAKUDOC=t/test-doc raku -I. bin/rakudoc Hash.classify-list generates the desired result. | |||
(after a rakudoc -b) | |||
tonyo: need to specify the inner doc/ folder, then everything works as expected. (see ticket). | 22:57 | ||
tonyo | ah | 23:00 | |
23:13
linkable6 left,
evalable6 left
23:14
evalable6 joined
23:16
linkable6 joined
|
|||
[Coke] | updated the README to note it. it was hidden in there. | 23:27 |