Eric Forste

@tbrowder let me know how I can help with this one. While working on docs issue https://github.com/Raku/doc/issues/4395 (documenting named arrays), I also added some subheadings that break up the very...

I can't access @*MODULES in the REPL (with and without modules loaded), nor from inside a script with modules loaded. Both usages yield the error message: Dynamic variable @*MODULES not...

> Looks like it’s something the user would set to impact functionality, not something that is defined by default. That would be pretty difficult to use if it's not documented...

see also docs issue https://github.com/Raku/doc/issues/1796

https://irclogs.raku.org/raku-doc/2025-11-21.html The present-day example (apparently written by JJ) is once again not compiling: https://docs.raku.org/type/Junction#Failures_and_exceptions `my $j = +any "not a number", "42", "2.1"; my @list = gather for $j ->...

I believe PR 4733 addresses this issue in full.

`last`, `next`, `redo`, and LABELs are all documented in the same document, but at the end, separated from the loop/while/until documentation by the discussions of `return`, `return-rw`, and `fail` I...

@librasteve, the original issue stated that you can in fact declare any number of subs before a unit package. I just tested declaring an empty `sub EXPORT` followed by a...

There was some discussion of that on the other issues linked above, and there's reluctance to document things that ROAST doesn't require, which makes sense, since all such behavior is...

So should I be trying to write my first ROAST tests then? I think for this one, we want to add it to the spec before changing the doc.