bisectable6

query

my $a = 42; say $a =:= $a || $a.WHAT =:= $a.WHAT

result

Bisecting: 2532 revisions left to test after this (roughly 11 steps)
[302346e956855b574e16dddae8d9958e0a568c59] Viki asked me to add my details
»»»»» Testing 302346e956855b574e16dddae8d9958e0a568c59
»»»»» Script output:
1
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing ca1acb727b0b81c190650796b4c24f0f6be75f45
»»»»» Script output:
True
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 99b186ba7348ba55c2827c5d2f6007ecf7a0ad3c
»»»»» Script output:
1
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing ae2c1dadf05db56c78ff6a10062ed059ba073b4d
»»»»» Script output:
True
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 951a441d10b57f5ac2570f7986785e6cf56c11a7
»»»»» Script output:
True
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 4d8c32a3f469218ebeade4dbec3b069c52f4f300
»»»»» Script output:
1
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing a832944d6ce7afe7826845d8af9072952db5c9d2
»»»»» Script output:
1
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 34244650772c415802802a3d3b0c2ecd69d32379
»»»»» Script output:
1
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing f94cb21ef5f78fe40f50832b168b95288f2a574e
»»»»» Script output:
1
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 0152316f56121ecd6236b4539308cb8341cec6d8
»»»»» Script output:
True
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 9ed4449db57cab39a115c5347387d5978bd56057
»»»»» Script output:
True
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing f8b3469439108fead043bab2bd27bde4bac50dca
»»»»» Script output:
True
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is different
»»»»» Therefore, marking this revision as “new”
»»»»» -------------------------------------------------------------------------
»»»»» Testing 5401a1aa8f12c360ccd3e4000dcdc65ad98c746a
»»»»» Script output:
1
»»»»» Script exit code: 0
»»»»» Bisecting by output
»»»»» Output on “old” revision is:
1
»»»»» The output is identical
»»»»» Therefore, marking this revision as “old”
»»»»» -------------------------------------------------------------------------
f8b3469439108fead043bab2bd27bde4bac50dca is the first new commit
commit f8b3469439108fead043bab2bd27bde4bac50dca
Author: Jonathan Worthington <jnthn@jnthn.net>
Date:   Tue Jan 31 16:46:33 2017 +0100

    Only generate static inline info when native args.
    
    Some years back, when Rakudo's optimizer was implemented, we didn't
    run on a VM that could do inlining. This is no longer the case, and
    it's much easier to do the analysis for correct semantic preservation
    in a VM and get it consistently right than it is in Rakudo. A VM can
    also only expend the effort on hot code. So, from now on we will only
    spit out static inline info for subs with natively typed parameters.
    These actually do get a notable benefit in generated code quality,
    certainly beyond what MoarVM can currently achieve without the help;
    JVM and JS backends will likely find it valuable too.
    
    This also fixes various discrepancies we were getting as a result of
    inlining of non-natives.

:040000 040000 33d3eac28756cd17b6369954a8e0fab320b33251 e5f8ac19050af438110b15ce27764028c746d784 M	src