doc
doc copied to clipboard
🦋 Raku documentation
1. Explain deprecation a bit. 2. Mention the environment variable that can silence this warning 3. Provide an example of how we coped with the recent class name change.
Extra clarification for fez versioning, indicate preference for fez, note that if module migrated to fez to remove from p6c
The X<> code syntax for creating 2 or more entries is almost not used and probably should go away
## Problem or new feature The `X` formatting code allows to index 2 and more entries under a single code, separated by a semicolon. However, this demands more complex code...
## Problem or new feature Data points: - Each =head leads to creation of an anchor to use in TOC (and possibly search entry if has X or uses keyword...
Consider the following code: ``` END { exit 0 } my atomicint $i; my @proms; for ^20 { @proms.push: start { exit ++⚛$i; } } await @proms; END { exit...
docs.raku.org/language/operators#postcircumfix_ should be docs.raku.org/language/operators#postfix_ And the first sentence there has an unhelpful comma, which could be eliminated with something like: > When applied to a container, the decont operator will...
In https://docs.raku.org/language/contexts#Sink we do not mention that user defined dynvars, even when they are defined quite globally, will not show up in `method sink`. This can lead to had to...
## Problem or new feature Links created with `L` don't render properly inside a table's rows. See image:  ## Suggestions If this a limitation of Pod, we could simply...
https://docs.raku.org/routine/encoding#class_IO::Handle has a list of encodings. We should duplicate this list on https://docs.raku.org/routine/encode or make the list discoverable in one location from both pages.
When doing `make` - [x] found duplicate index entry is (inheritance) at #i45 #i679 - [x] found duplicate index entry :{} at #i853 #i855 - [x] found duplicate index entry...