Skip to content

Commit c4db4e1

Browse files
committed
Remove mention of outcome in Channel spec
It is mentioned in the "outcome" spec, so premature here.
1 parent 6e8b79e commit c4db4e1

File tree

1 file changed

+0
-8
lines changed

1 file changed

+0
-8
lines changed

S17-concurrency.pod

Lines changed: 0 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -411,14 +411,6 @@ calls to a channel return the same promise, not a new one.
411411
While C<receive> blocks until it can read, C<poll> takes a message from the
412412
channel if one is there or immediately returns C<Nil> if nothing is there.
413413

414-
The C<outcome> construct also works on channels, and will try to receive
415-
values from the any C<Channel> that has value(s) available until they are
416-
all closed.
417-
418-
outcome {
419-
whenever $channel { take $_ }
420-
}
421-
422414
This is such a common pattern that we make a channel in list context behave
423415
that way:
424416

0 commit comments

Comments
 (0)