In role Iterator§| docs.raku.org
Raku highlighting| docs.raku.org
Raku is built on a metaobject layer. That means that there are objects (the metaobjects) that control how various object-oriented constructs (such as classes, roles, methods, attributes or enums) behave.| 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
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
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
One often needs to refer to a specific element (or slice of elements) from a collection or data structure. Borrowing from mathematical notation where the components of a vector v would be referred to as v₁, v₂, v₃, this concept is called "subscripting" (or "indexing") in Raku.| docs.raku.org