Rules / Types, classes & roles / exception

X::Phaser::PrePost Reference

Error due to a false return value of a PRE/POST phaser

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 phaser #

method phaser(--> Str:D)

Returns Str:D.

Returns the name of the failed phaser, "PRE" or "POST".

method condition #

method condition(--> Str:D)

Returns Str:D.

Returns the part of the source code that describes the phaser condition.

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 rakudo-differs

class X::Phaser::PrePost is Exception { }

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

sub f($x) { PRE { $x ~~ Int } };
f "foo";
CATCH { default { put .^name, ': ', .Str } };
# OUTPUT: X::Phaser::PrePost: Precondition '{ $x ~~ Int }' failed«␤»
Documentation

Rakudo
X::Phaser::PrePost: Precondition '{ $x ~~ Int }' failed
Raku++

Raku++ matches the documentation; Rakudo does not. This is the one class where neither engine can be assumed right: it may be a stale doc that Raku++ was built from, or it may be a Rakudo bug that the documentation predates. Each case is examined individually.

Not yet examined. Which of these is correct has not been established — do not treat either engine as settled here.