Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Signatures appear inside parentheses after subroutine and method names, on blocks after a -> or <-> arrow, as the input to variable declarators like my, or as a separate term starting with a colon.| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
These routines are defined in different files along with one or several other classes, but are not actually attached to any particular class or role.| docs.raku.org
The lifetime (execution timeline) of a program is broken up into phases. A phaser is a block of code called during a specific execution phase.| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku borrows many concepts from human language. Which is not surprising, considering it was designed by a linguist.| docs.raku.org
Abstract class§| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Raku highlighting| docs.raku.org
Routines are one of the means Raku has to reuse code. They come in several forms, most notably Methods, which belong in classes and roles and are associated with an object; and functions (also called subroutines or Subs, for short), which can be called independently of objects.| docs.raku.org
Variables are symbolic names for values or containers. Variable declarations or assignment of values may create a container on the fly. Variable names can start with or without a special character called a sigil, followed optionally by a second special character named twigil and then an identifier.| docs.raku.org