In Operators§| docs.raku.org
In common with most modern programming languages, Raku is designed to support parallelism, asynchronicity and concurrency. Parallelism is about doing multiple things at once. Asynchronous programming, which is sometimes called event driven or reactive programming, is about supporting changes in the program flow caused by events triggered elsewhere in the program. Finally, concurrency is about the coordination of access and modification of some shared resources.| docs.raku.org
Raku highlighting| docs.raku.org
In Backtrace§| 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
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 borrows many concepts from human language. Which is not surprising, considering it was designed by a linguist.| 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
In Nil§| docs.raku.org
In Supply§| docs.raku.org
In ObjAt§| docs.raku.org
In role Iterable§| docs.raku.org
In List§| 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
Statements§| docs.raku.org
In Control flow§| docs.raku.org
In List§| docs.raku.org
In Any§| docs.raku.org
Definition of a Raku type§| docs.raku.org
In Any§| docs.raku.org
See creating operators on how to define new operators.| docs.raku.org