Skip to content

Commit

Permalink
Change mentions of Rakudo release 2019.01 → 2019.03
Browse files Browse the repository at this point in the history
2019.01 did not come out.
  • Loading branch information
taboege committed May 20, 2019
1 parent 0fa1b52 commit 71eda86
Show file tree
Hide file tree
Showing 8 changed files with 10 additions and 10 deletions.
4 changes: 2 additions & 2 deletions doc/Type/Bag.pod6
Expand Up @@ -77,7 +77,7 @@ Of course, you can also create a C<Bag> with the C<.new> method.
my $breakfast = Bag.new( <spam eggs spam spam bacon spam> );
Since 6.d (2019.01 and later) you can also use this syntax for parameterization
Since 6.d (2019.03 and later) you can also use this syntax for parameterization
of the C<Bag>, to specify which type of values are acceptable:
# only allow strings (Str) in the Bag
Expand All @@ -93,7 +93,7 @@ Finally, you can create Bag masquerading as a hash by using the C<is> trait:
say %b<a>; # True
say %b<d>; # False
Since 6.d (2019.01 and later), this syntax also allows you to specify the
Since 6.d (2019.03 and later), this syntax also allows you to specify the
type of values you would like to allow:
# limit to strings
Expand Down
2 changes: 1 addition & 1 deletion doc/Type/BagHash.pod6
Expand Up @@ -81,7 +81,7 @@ You can also create C<BagHash> masquerading as a hash by using the C<is> trait:
say %bh<b>; # 2
say %bh<d>; # 0
Since 6.d (2019.01 and later) it is also possible to specify the type of values
Since 6.d (2019.03 and later) it is also possible to specify the type of values
you would like to allow in a C<BagHash>. This can either be done when calling
C<.new>:
Expand Down
2 changes: 1 addition & 1 deletion doc/Type/Mix.pod6
Expand Up @@ -70,7 +70,7 @@ declare them; in that case, we can employ C<is> to declare their type:
say %n.^name; # OUTPUT: «Mix␤»
say %n; # OUTPUT: «Mix(a(2), c(3.14))␤»
Since 6.d (2019.01 and later) it is also possible to specify the type of values
Since 6.d (2019.03 and later) it is also possible to specify the type of values
you would like to allow in a C<Mix>. This can either be done when calling
C<.new>:
Expand Down
2 changes: 1 addition & 1 deletion doc/Type/MixHash.pod6
Expand Up @@ -66,7 +66,7 @@ the mix, and the (cumulative) values become the associated numeric weights:
say $n.keys.map(&WHAT); # OUTPUT: «((Str) (Str))␤»
say $n.pairs; # OUTPUT: «(a => 2 c => 3.14)␤»
Since 6.d (2019.01 and later) it is also possible to specify the type of values
Since 6.d (2019.03 and later) it is also possible to specify the type of values
you would like to allow in a C<MixHash>. This can either be done when calling
C<.new>:
Expand Down
2 changes: 1 addition & 1 deletion doc/Type/Parameter.pod6
Expand Up @@ -286,7 +286,7 @@ If the parameter has a
L<sub-signature|/type/Signature#Destructuring_Parameters>,
returns a C<Signature> object for it. Otherwise returns C<Any>.
=head1 Runtime creation of Parameter objects (6.d, 2019.01 and later)
=head1 Runtime creation of Parameter objects (6.d, 2019.03 and later)
Parameter.new( ... )
Expand Down
4 changes: 2 additions & 2 deletions doc/Type/Set.pod6
Expand Up @@ -61,7 +61,7 @@ Of course, you can also create a C<Set> with the C<.new> method.
my $fruits = Set.new( <peach apple orange apple apple> );
Since 6.d (2019.01 and later) you can also use this syntax for parameterization
Since 6.d (2019.03 and later) you can also use this syntax for parameterization
of the C<Set>, to specify which type of values are acceptable:
# only allow strings (Str) in the Set
Expand All @@ -77,7 +77,7 @@ Finally, you can create Set masquerading as a hash by using the C<is> trait:
say %s<a>; # True
say %s<d>; # False
Since 6.d (2019.01 and later), this syntax also allows you to specify the
Since 6.d (2019.03 and later), this syntax also allows you to specify the
type of values you would like to allow:
# limit to strings
Expand Down
2 changes: 1 addition & 1 deletion doc/Type/SetHash.pod6
Expand Up @@ -92,7 +92,7 @@ You can also create C<SetHash> masquerading as a hash by using the C<is> trait:
say %sh<a>; # True
say %sh<d>; # False
Since 6.d (2019.01 and later) it is also possible to specify the type of values
Since 6.d (2019.03 and later) it is also possible to specify the type of values
you would like to allow in a C<SetHash>. This can either be done when calling
C<.new>:
Expand Down
2 changes: 1 addition & 1 deletion doc/Type/Signature.pod6
Expand Up @@ -1078,7 +1078,7 @@ Defined as:
Throws C<X::Cannot::Capture>.
=head1 Runtime creation of Signature objects (6.d, 2019.01 and later)
=head1 Runtime creation of Signature objects (6.d, 2019.03 and later)
=for code :preamble<role Type {}>
Signature.new(params => (...), returns => Type, arity => 1, count => 1)
Expand Down

0 comments on commit 71eda86

Please sign in to comment.