27 Sep 2025 | |||
[Coke] | 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 | |
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 | ||
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 | ||
28 Sep 2025 | |||
doc/main: 0023c058d3 | (Will Coleda)++ | doc/Type/Routine.rakudoc Fix code wrapper on output |
00:00 | ||
[Coke] | Thanks, folks | ||
Geth | doc/raiph-patch-3: 9a1b43dd94 | raiph++ (committed using GitHub Web editor) | doc/Type/Routine.rakudoc Further simplify `say` line of `is rw` example in Routine.rakudoc Imo the change just made was a solid step in the right direction, but didn't go far enough. I have saved a full rationale in a gist if whoever reads this (@coke?) doesn't agree that the output is still far too complex for good reference doc. (As a tangent, the routine code in the example is also far too complex for good reference doc for `is rw`. But without reading some large swathe of the doc I wouldn't know whether there's a significant negative impact if we radically simplify that code. So I've focused for this PR on just improving further on the good direction @schultzdavid took the `say` part.) |
00:45 | |
doc: raiph++ created pull request #4625: Further simplify display by `say` line of `is rw` example in Routine.rakudoc |
00:59 | ||
doc: schultzdavid++ created pull request #4626: Update section `method wrap` in Routine.rakudoc: Link to Re-dispatching |
14:14 | ||
doc/main: f22a3ef261 | schultzdavid++ (committed using GitHub Web editor) | doc/Type/Routine.rakudoc Update section `method wrap` in Routine.rakudoc: Link to definition of redispatching tools (#4626) Since `callsame`, `callwith` etc. are mentioned in the text, link to where they are defined, namely to docs.raku.org/language/functions#Re-dispatching |
14:33 | ||
doc/main: db13317183 | (Will Coleda)++ | doc/Type/Routine.rakudoc whitespace |
14:34 | ||
ds7832 is schultzdavid | 14:35 | ||
[Coke] | ah, hi | 14:37 | |
FYI, that whitespace fix was on your PR, if you could test changes with util/test_modified.sh, that'd be great. saves me a few seconds. :) | 14:38 | ||
thanks for the submittals. | |||
ds7832 | Ah nice, I'll see to get the testing tools set up :) | 14:42 |