bisectable6

query

old=2024.01 say 10.3 mod 3.3

result

Bisecting: 177 revisions left to test after this (roughly 8 steps)
[85e07ec8921eec74cfc44b9566edfbb4469e8966] We already calculated the HOW, no need to look up again
»»»»» Testing 85e07ec8921eec74cfc44b9566edfbb4469e8966
»»»»» Script output:
0.4

»»»»» 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 4f64b4876b729841cf237e08052c4943098301ea
»»»»» Script output:
0.4

»»»»» 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 492c1828f40872c88f75536163e300fe6eefce02
»»»»» Script output:
0.4

»»»»» 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 7ca96bbd90f79bfa9d51d80b93e62506eb2e44c5
»»»»» Script output:
Cannot resolve caller infix:<div>(Rat:D, Rat:D); none of these signatures matches:
    (Int:D $a, Int:D $b --> Int:D)
    (int $a, int $b --> int)
    (uint $a, uint $b --> uint)
  in block <unit> at /tmp/WxDr51jNqf line 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 5c9156e268b103997f451f0ed2d0f4ebcd9e6698
»»»»» Script output:
0.4

»»»»» 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 512978791d25c00fe9e22f0a3b374f67507049d7
»»»»» Script output:
0.4

»»»»» 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 3eba92f5bf9797654e2e05da9ce2c62576397960
»»»»» Script output:
0.4

»»»»» 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 71c0151aa7c09cb86ed74960db818f7429f88fb7
»»»»» Script output:
0.4

»»»»» 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”
71c0151aa7c09cb86ed74960db818f7429f88fb7 is the first new commit
commit 71c0151aa7c09cb86ed74960db818f7429f88fb7
Author: Daniel Green <ddgreen@gmail.com>
Date:   Tue Jun 7 15:38:05 2022 -0400

    Add Int/Real coercing versions of `infix:<div|mod>`
    
    This makes them consistent with the other operators, so e.g., `say "6"
    div 3` now prints `2`, instead of
    `Calling infix:<div>(Str, Int) will never work with any of these multi signatures:
        (Int:D \a, Int:D \b --> Int:D)
        (int $a, int $b --> int)
        (uint $a, uint $b --> uint)`
    
    Fixes https://github.com/Raku/problem-solving/issues/326

 src/core.c/Int.rakumod  | 6 ++++++
 src/core.c/Real.rakumod | 1 +
 2 files changed, 7 insertions(+)