Skip to content

Commit f04b29c

Browse files
committed
Reviews new and clarifies, refs #2703
1 parent bd3534f commit f04b29c

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

doc/Type/Junction.pod6

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ if a() | b() | c() {
9898
}
9999
=end code
100100
101-
Junctions are meant to be used as matchers in Boolean context; introspection
101+
Junctions are meant to be used as matchers in a Boolean context; introspection
102102
of junctions is not supported. If you feel the urge to introspect a junction,
103103
use a L<Set|/type/Set> or a related type instead.
104104
@@ -231,12 +231,16 @@ Defined as:
231231
multi method new(Junction: \values, Str :$type!)
232232
multi method new(Junction: Str:D \type, \values)
233233
234-
Constructor to define a new Junction from the type that defines a Junction and
234+
Constructor to define a new junction from the type that defines it and
235235
a set of values.
236236
237237
my $j = Junction.new(<Þor Oðinn Loki>, type => "all");
238238
my $n = Junction.new( "one", 1..6 )
239239
240+
The main difference between the two multis is how the type of the C<Junction>
241+
is passed as an argument; either positionally as the first argument, or as a
242+
named argument using C<type>.
243+
240244
=head2 method defined
241245
242246
Defined as:

0 commit comments

Comments
 (0)