bisectable6

query

say "REGIONAL INDICATOR SYMBOL LETTER A".uniparse.NFD

result

Bisecting: 145 revisions left to test after this (roughly 7 steps)
[014f1712c66f2bf29b89246065eb344aea87c336] Make |(1,2,3) xx 42 about 3x faster
»»»»» Testing 014f1712c66f2bf29b89246065eb344aea87c336
»»»»» Script output:
NFD:0x<1f1e6>

»»»»» 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 e543c890ad58d4c707f734035532090e418a379a
»»»»» Script output:
NFD:0x<1f1e6>

»»»»» 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 d9ce5e9b82fe1199fa669f0026d835688b1a9682
»»»»» Script output:
NFD:0x<1f1e6>

»»»»» 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 d4f53ed5d99d76b263fb0f2417989960a60151df
»»»»» Script output:
NFD:0x<1f1e6>

»»»»» 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 cf7b01ef80ea80c17fe470aed913bf4a3f060dee
»»»»» Script output:
No such method 'uniparse' for invocant of type 'Str'
  in block <unit> at /tmp/syZnq0BN22 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 5eed2b002010bcc64a20084b87ef8c9b9ee07016
»»»»» Script output:
NFD:0x<1f1e6>

»»»»» 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 2a8287cf89966c4cd77e6889706a7abac170da01
»»»»» Script output:
NFD:0x<1f1e6>

»»»»» 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 e5c38ad67994271c5674e2c6deee918532f09be9
»»»»» Script output:
No such method 'uniparse' for invocant of type 'Str'
  in block <unit> at /tmp/syZnq0BN22 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”
2a8287cf89966c4cd77e6889706a7abac170da01 is the first new commit
commit 2a8287cf89966c4cd77e6889706a7abac170da01
Author: Zoffix Znet <cpan@zoffix.com>
Date:   Thu Dec 21 19:28:05 2017 -0500

    Rename Str.parse-names to Str.uniparse
    
    The original name was chosen to align with `.parse-base` that parses out
    base-X numbers out strings. However, we have a whole block of more closely
    related routines all named in `.uni*` format, so it makes sense for this
    routine's naming to align with those. They are: `infix:<unicmp>`,
    `unimatch`, `uniname`, `uninames`, `unival`, `univals`, `uniprop`,
    `uniprop-bool`, `uniprop-int`, `uniprop-str`, `uniprops`.
    
    Refs:
    https://github.com/perl6/6.d-prep/commit/efa24f68eddc8091a4d5da41bfeeeb4
    https://irclog.perlgeek.de/perl6-dev/2017-12-21#i_15609653

:040000 040000 9678775bf5d7717f2469fb3d8fa6af23fa04985a 93bb87554a8a4fa1603c391894b631ed775b8d76 M	src
:040000 040000 24fa99a29e712ef93ae12949424b6200005dd73b e851a21baf902c9dc6d4f57db1b9e2c573c8028e M	t