bisectable6

query

multi sub infix:<||=>($a, $b) is equiv(&infix:<+=>) { $a || $b }; my $foo = 0; $foo ||= 1;

result

Bisecting: 204 revisions left to test after this (roughly 8 steps)
[8ab6e019c67df6bd37630a251b72b87558014c13] Make R:I.DwimIterator a method
»»»»» Testing 8ab6e019c67df6bd37630a251b72b87558014c13
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/r5ZpgtYoe6
Routine given to equiv does not appear to be an operator
at /tmp/r5ZpgtYoe6:1

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 1dc34d847102ad71e100112ae92ad50d9f2e96d4
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 870b11b759379f9bc29d96d581f91b852dca0bf3
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/r5ZpgtYoe6
Routine given to equiv does not appear to be an operator
at /tmp/r5ZpgtYoe6:1

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 8f3476d5d4ddcd4acb353428038e8b91bd891daa
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 9ad94d783bf3595873297f4f557aa6f6064e2821
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 731d58749584529a669dbd3c1285d934439aa1c6
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing a7ccfc6f808f2d45fff4993917dc93cbbf8694a6
»»»»» Script output:

»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing d7d76b7dcfe0afb260c26c509ba68cf324475987
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/r5ZpgtYoe6
Routine given to equiv does not appear to be an operator
at /tmp/r5ZpgtYoe6:1

»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 1
»»»»» Note that on “old” revision exit code is normally 0, you are probably trying to find when something was fixed
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
a7ccfc6f808f2d45fff4993917dc93cbbf8694a6 is the first new commit
commit a7ccfc6f808f2d45fff4993917dc93cbbf8694a6
Author: Elizabeth Mattijsen <liz@dijkmat.nl>
Date:   Mon Jan 9 14:38:58 2017 +0100

    Move .prec from Routine to Code
    
    Turns out Blocks and WhateverCode also need to have a .prec to allow
    for easy checking of precedence of operators in metaops.

 src/core/Code.pm    | 4 ++++
 src/core/Routine.pm | 4 ----
 2 files changed, 4 insertions(+), 4 deletions(-)