Coverage
Every construct the official documentation describes, and what this site measures about each one. The list is not a guess — it is derived from the documentation itself, so nothing can hide. The pages are generated: machine-extracted facts, parse probes against this implementation, and examples checked on both engines before they are allowed to appear.
By topic
| Topic | Constructs |
|---|---|
| How to read these rules | 1 |
| Terms & literals | 16 |
| Operators | 164 |
| Types, classes & roles | 355 |
Where Raku++ does not parse the spelling
Probed directly: a minimal use of each construct is fed to the interpreter and classified by whether it parses. 14 spellings do not — but read the two groups separately, because they mean very different things.
Unicode spellings (11)
These are alternative spellings, not missing operators. Raku lets many operators be written with a mathematical symbol as well as in ASCII — ⩵ for ==, ≼ for (<+). Raku++ not accepting the symbol says nothing about the operator itself: == works exactly as expected. Where the documentation puts a working spelling under the same heading, it is named on the card.
« »method call≡chaining≢chaining≼chaining≽chaining⊄chaining⊅chaining⊈chaining⊉chaining⩵works as ==⩶chainingASCII spellings (3)
These are the ones that matter: an ordinary spelling the interpreter cannot parse at all.