@@ -78,7 +78,7 @@ my $eat =
78
78
$eat.perform();
79
79
= end code
80
80
81
- X < |classes ,state >
81
+ X < |Tutorial,class;Tutorial ,state >
82
82
= head1 X < Class|Tutorial,class;Tutorial,state >
83
83
84
84
Raku, like many other languages, uses the C < class > keyword to define a
@@ -173,7 +173,7 @@ so external code can modify the value of the attribute.
173
173
= for code
174
174
has &!callback is built;
175
175
176
- X < |traits,is built >
176
+ X < |Types, traits;Types ,is built >
177
177
By default private attributes are not automatically set by the default constructor. (They are private after
178
178
all.) In the above example we want to allow the user to provide the initial value but keep the attribute
179
179
otherwise private. The C < is built > trait allows to do just that.
@@ -190,7 +190,7 @@ The C<is built> trait was introduced in Rakudo version 2020.01.
190
190
191
191
= head2 C < is required > trait
192
192
193
- X < |traits,is required >
193
+ X < |Types, traits;Types ,is required >
194
194
Providing a value for an attribute during initialization is optional by default. Which in the task example
195
195
makes sense for all three, the C < &!callback > , the C < @!dependencies > and the C < $.done > attribute. But lets say
196
196
we want to add another attribute, C < $.name > , that holds a tasks name and we want to force the user to
@@ -269,7 +269,7 @@ is used, the variable is visible via their fully qualified name (FQN), while
269
269
lexically scoped C < my > variables are "private". This is the exact behavior that
270
270
C < my > and C < our > also show in non class context.
271
271
272
- X < |static >
272
+ X < |Types, static >
273
273
I < Class variables > act similarly to I < static > variables in many other programming
274
274
languages.
275
275
0 commit comments