Rules / Types, classes & roles / exception

X::Proc::Async::CharsOrBytes Reference

Error due to tapping the same Proc::Async stream for both text and binary reading

What it is #

Routines #

Signatures are reproduced from the documentation, including their declared return types. A routine listed here is part of the type's published interface; whether Raku++ implements it is a separate question, answered by the examples below.

method handle #

method handle(X::Proc::Async::CharsOrBytes:D: --> Str:D)

Returns Str:D.

Returns the name of the handle that was accessed both for text and for binary data, stdout or stderr.

Examples, run three ways #

Every example below comes from the official documentation, together with the output that documentation asserts. Each was then executed by Rakudo and by Raku++ when this page was built. Where the three agree, one result is shown; where they do not, all three are — because which of them is wrong is exactly the information worth having.

1 no-output · 1 rakupp-differs

class X::Proc::Async::CharsOrBytes is Exception {}

Not executed: the documentation states no expected output for this example.

my $proc = Proc::Async.new('echo');
$proc.stdout.tap(&print);
$proc.stdout(:bin).tap(&print);
CATCH { default { put .^name, ': ', .Str } };
# OUTPUT: «X::Proc::Async::CharsOrBytes: Can only tap one of chars or bytes supply for stdout␤»
Documentation
X::Proc::Async::CharsOrBytes: Can only tap one of chars or bytes supply for stdout
Rakudo
X::Proc::Async::CharsOrBytes: Can only tap one of chars or bytes supply for stdout
Raku++

Raku++ disagrees with both the documentation and Rakudo — a defect.