11:21
finanalyst joined
12:31
finanalyst left
15:32
librasteve_ joined
16:02
finanalyst joined
|
|||
[Coke] | we have a test in raku/doc that checks for things like C<Mu> to ensure that we are also linking to the Mu type. | 17:27 | |
there are false positives like C<utf8> which is referring to, e.g. utf8 in general, or some other language's type of Int that has the same name... Any suggestion on how to mark the docs so that a) it doesn't change the render, and b) the test knows not to complain? | 17:28 | ||
maybe C<Z<>utf8> ? | 17:31 | ||
can't be that because the C<> causes the Z<> to be literal | 17:40 | ||
C<utf8>Z<> seems magical, but would that be OK? | 17:41 | ||
Geth | doc/main: 64558ec3e4 | (Will Coleda)++ | doc/Language/slangs.rakudoc format type correctly |
18:16 | |
18:52
finanalyst left
|
|||
Geth | doc: arkiuat++ created pull request #4623: Update Str.rakudoc (.lines & .words return Seq, not List) |
21:30 | |
doc: schultzdavid++ created pull request #4624: Update section `trait is rw` in Routine.rakudoc |
21:41 | ||
21:43
ds7832 joined
|
|||
Geth | doc/main: 2594bfc90d | schultzdavid++ (committed using GitHub Web editor) | doc/Type/Routine.rakudoc Update section `trait is rw` in Routine.rakudoc (#4624) With Rakudo Star v2025.08, the output of the code example is different than currently stated in the doc page. The apparent reason is that `say %hash.raku` now produces output in a different format. In this specific example, it's `{:some(${:key($[Any, [Any, Any, "autovivified"]])})}` Since this is rather unwieldy, I propose changing `say %hash.raku` to `say %hash`, with which the output is {some => {key => [(Any) [(Any) (Any) autovivified]]}} The same output would also be produces by `say %hash.gist`. |
23:36 | |
doc/main: ff67e951ee | (Eric Forste)++ (committed using GitHub Web editor) | doc/Type/Str.rakudoc Update Str.rakudoc (#4623) Change "list" to L<C<Seq>|/type/Seq> where this is relevant (.lines, .words) |
23:59 |