New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Precedence of prefix ops used as functions (e.g. not(3)) #988
Comments
From @skidsAccording to S03, when used in a functional manner, precedence S03: "not($x) + 1 # means (not $x) + 1" Currently the examples in S03 produce different results than specced. See IRC discussion here: http://irclog.perlgeek.de/text.pl?channel=perl6;date=2009-05-11 |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S03-operators/not.t commit c10b7c5a53c3857fdb648052a80478d16ddf52aa [t/spec] Test for RT #65556 Inline Patchdiff --git a/t/spec/S03-operators/not.t b/t/spec/S03-operators/not.t
index 35856d8..7784e84 100644
--- a/t/spec/S03-operators/not.t
+++ b/t/spec/S03-operators/not.t
@@ -1,6 +1,6 @@
use v6;
use Test;
-plan 13;
+plan *;
sub not_ok($cond,$desc) {
if $cond {
@@ -21,12 +21,17 @@ not_ok(not "x", 'not "x" is false');
my $a = 1; not_ok(not $a, 'not $not_var is false');
my $b = 0; not_ok(!(not $b), 'not $false_var is not false');
+#?rakudo todo 'RT 65556'
+is (not($b) + 1), ((not $b) + 1), 'not($b) is (not $b)';
+
ok( not(not 42), "not(not 42) is true");
-ok(!not(not 0), "not(not 0) is true");
+ok(!not(not 0), "not(not 0) is false");
is(not Bool::True, Bool::False, "'Bool::True' is not 'Bool::False'");
is(not Bool::True, False, "'Bool::True' is not 'False'");
is(not True, False, "'True' is not 'False'");
is(not True, Bool::False, "'True' is not 'Bool::False'");
+done_testing;
+
# vim: ft=perl6 |
The RT System itself - Status changed from 'new' to 'open' |
From @moritzBrian S. Julin (via RT) wrote:
The test now passes, so I guess the problem is now solved. |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#65556 (status was 'resolved')
Searchable as RT65556$
The text was updated successfully, but these errors were encountered: