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
infix:<!eq> shouldn't differ from infix:<ne> when applied to junctions in Rakudo #1787
Comments
From @masak<pmichaud> actually, $i !~~ any(|$nth) should be the same as |
From @jnthnOn Wed May 26 05:53:47 2010, masak wrote:
Now it's all nicely consistent...
Given to moritz++ for spectests. Thanks, Jonathan |
The RT System itself - Status changed from 'new' to 'open' |
@moritz - Status changed from 'open' to 'resolved' |
From @kylehaThis is an automatically generated mail to inform you that tests are now available in t/spec/S03-junctions/autothreading.t commit 95286058005835b101d98e9f2d55549f5fe2aa64 [t/spec] tests for RT #75368 and new spec wrt autothreading over negated operators Inline Patchdiff --git a/t/spec/S03-junctions/autothreading.t b/t/spec/S03-junctions/autothreading.t
index ec61ecb..2e32c6b 100644
--- a/t/spec/S03-junctions/autothreading.t
+++ b/t/spec/S03-junctions/autothreading.t
@@ -1,7 +1,7 @@
use v6;
use Test;
-plan 77;
+plan 83;
{
# Solves the equation A + B = A * C for integers
@@ -285,4 +285,18 @@ plan 77;
is $c, 6, 'do autothread over blocks with explicit Any';
}
+# used to be RT #75368
+# L<S03/Junctive operators/Use of negative operators with junctions>
+{
+ my Mu $x = 'a' ne ('a'|'b'|'c');
+ ok $x ~~ Bool, 'infix:<ne> collapses the junction (1)';
+ ok $x !~~ Junction, 'infix:<ne> collapses the junction (2)';
+ nok $x, '... and the result is False';
+
+ my Mu $y = 'a' !eq ('a'|'b'|'c');
+ ok $y ~~ Bool, 'infix:<!eq> collapses the junction (1)';
+ ok $y !~~ Junction, 'infix:<!eq> collapses the junction (2)';
+ nok $y, '... and the result is False';
+}
+
# vim: ft=perl6 |
Migrated from rt.perl.org#75368 (status was 'resolved')
Searchable as RT75368$
The text was updated successfully, but these errors were encountered: