It's the same with && and ||:
➜ :<&&>(1, -> {say 2}); # 2
➜ say 1 && -> {say 2}; # -> { #`(Block|169403552312) ... }
➜ :<||>(0, -> {say 2}); # 2
➜ say 0 || -> {say 2}; # -> { #`(Block|786414142008) ... }
And also with the loose-precedence versions `and`,
# New Ticket Created by Zoffix Znet
# Please include the string: [perl #131932]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=131932 >
The first example below evaluates the code block, while the two examples after
it never
I had to revert one of the nqp commits related to .parse:
https://github.com/perl6/nqp/commit/d4d77b66c46c57de800b147df61fe486b4486acd
Here's a ticket for the module that was affected by the change:
https://github.com/p6-css/CSS-Module-p6/issues/10
Most certainly we want this change back ASAP,
The change was moved to v6.d in this commit:
https://github.com/rakudo/rakudo/commit/d2278b471cb0bd691dc7a1235fbcb9318ff5d61f
On 2017-08-17 08:50:48, alex.jakime...@gmail.com wrote:
> See this commit:
>
https://github.com/rakudo/rakudo/commit/9501edae4f73a970e3270e3b0336a7b3045d3329
>
> These
It was fixed in this commit:
https://github.com/MoarVM/MoarVM/commit/5363a0742d9ea7183200a747c2d7531e82bc5c71
samcv++
Tests needed.
On 2017-08-18 12:48:20, alex.jakime...@gmail.com wrote:
> The issue happens in Email::Simple (one of its tests is now failing,
> but it was ok in 2017.07).
>
>
bisectable6: say .any ~~ m/a/;
smls, On both starting points (old=2015.12 new=e3e29c5)
the exit code is 0 and the output is identical as well
smls, Output on both points: «False»
The problem only appears if `m//` is used directly as the RHS of `~~`:
$_ = 'a' | 'b';
say m/a/; # any(｢a｣, Nil)
say $_ ~~ m/a/; # False
say $_ ~~ { m/a/ }; # any(｢a｣, Nil)
