Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki
Set by [Coke] on 23 May 2022.
08:06 sena_kun joined 08:50 Xliff left
Geth doc/tonyo/dists-update: 165562c2a7 | tonyo++ | doc/Language/modules.rakudoc
mention dist tools
14:54
doc: tonyooooooo++ created pull request #4280:
mention dist tools
14:55
doc/tonyo/dists-update: 165562c2a7 | tonyo++ | doc/Language/modules.rakudoc
mention dist tools
14:56
doc: tony-o++ created pull request #4281:
mention dist tools
15:01
doc/tonyo/dists-update: 03da80d9d0 | (Will Coleda)++ | xt/pws/code.pws
new word
15:05
doc/main: dee8348e4d | tony-o++ (committed using GitHub Web editor) | 2 files
mention dist tools (#4281)

  * mention dist tools
15:06
lizmat so I started to work on supporting pod in RakuAST 16:06
and I must admit, I never looked much at the innards of the Pod::Block hierarchy, or the contents of $=pod 16:07
but what a mess
[Coke] no doubt. 16:09
lizmat I guess I will need to re-implement this mess, but my ideas are now forming towards a different hierarchy of RakuAST classes 16:10
that will either QAST to the old Pod::Block mess, or to a new RakuDOC hierarchy that would be much more user friendly 16:11
does that feel like a plan ?
I mean, that: 16:12
=head1 Foo
bar
codegennes to a Pod::Heading in which the contents is an array with a Doc::Para with the title of the header as the first element? 16:13
ah, I now see that you can actually have additional lines after a =head1 and still have that be part of the contents 16:18
TIL
do we actually have usage of that feature: I always interpreted it as a title, not as a paragraph
Ah, I guess that comes from =head1 being short for =begin head1 16:27
but oddly enough both codegenn to a Pod::Heading 16:28
Geth doc/main: 3477c601c0 | (Will Coleda)++ | doc/Language/5to6-perlfunc.rakudoc
remove duplicate word
17:51
21:54 sena_kun left 22:03 Geth left, Geth joined 22:23 sena_kun joined 22:26 sena_kun left