Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created Jul 1, 2020
Embed
What would you like to do?
bisectable6
old=2020.01 "aaa" ~~ /(.)(.)(.)/; .say for $/
Bisecting: 488 revisions left to test after this (roughly 9 steps)
[0fba27d74685ccbe0e9e4f5520c2efcd2d9a4f0d] Streamlining Rakudo::SEQUENCE.iterator (1/N)
»»»»» Testing 0fba27d74685ccbe0e9e4f5520c2efcd2d9a4f0d
»»»»» Script output:
「aaa」
0 => 「a」
1 => 「a」
2 => 「a」
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 85fa569ce3e1e3632d4e46fac7f800e6fd2c6069
»»»»» Script output:
Died with X::Method::NotFound
in block <unit> at /tmp/ldwoQxYXYe line 1
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» 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 42a303ecf5c36bcbc0c3a5332fd4a0719c08a417
»»»»» Script output:
「aaa」
0 => 「a」
1 => 「a」
2 => 「a」
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 d6576888a18b20711b9b828e869dc8752620b78b
»»»»» Script output:
「aaa」
0 => 「a」
1 => 「a」
2 => 「a」
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 ef90599e2b6fde85385633b373b706b89d546763
»»»»» Script output:
「aaa」
0 => 「a」
1 => 「a」
2 => 「a」
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 25f8395cf59e2067880b5963026d78f31518741b
»»»»» Script output:
「aaa」
0 => 「a」
1 => 「a」
2 => 「a」
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» 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 4297cb051d2ec578c78797528ee5cf4bfcbf15a9
»»»»» Script output:
Died with X::Method::NotFound
in block <unit> at /tmp/ldwoQxYXYe line 1
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» 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 438c1d2fa624acdec703af34962f3a57f8c39e71
»»»»» Script output:
Died with X::Method::NotFound
in block <unit> at /tmp/ldwoQxYXYe line 1
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» 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 88d98225a4df61473ff5b935561719c56b04d1c2
»»»»» Script output:
Died with X::Method::NotFound
in block <unit> at /tmp/ldwoQxYXYe line 1
»»»»» Script exit code: 1
»»»»» Bisecting by exit code
»»»»» Current exit code is 1, exit code on “old” revision is 0
»»»»» 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 ef0c457bab8b702e299841152fbf4723ba9cae66
»»»»» Script output:
「aaa」
0 => 「a」
1 => 「a」
2 => 「a」
»»»»» Script exit code: 0
»»»»» Bisecting by exit code
»»»»» Current exit code is 0, exit code on “old” revision is 0
»»»»» If exit code is not the same as on “old” revision, this revision will be marked as “new”
»»»»» Therefore, marking this revision as “old”
88d98225a4df61473ff5b935561719c56b04d1c2 is the first new commit
commit 88d98225a4df61473ff5b935561719c56b04d1c2
Author: Elizabeth Mattijsen <liz@wenzperl.nl>
Date: Sun May 10 22:37:25 2020 +0200
Normalizing IO::Handle.say/put/print/note, part 2
The &say sub now performs all of the .gist + newline logic and then
dispatches to .print. The advantage of this is that we do not need
any additional logic / checks for modules that pretend to be $*OUT.
This also removes the IO::Handle.say(Str:D) candidate: even though a
Str may be passed to IO::Handle.say, it should *still* call the .gist
method on it, as it can have a non noop .gist method mixed in (roast
actually tests for this in the &sub case).
This commit also creates a single proto say for all of Rakudo.
This commit also adds Mu.say candidates to take care of those classes
that pretend to do the $*OUT API and which do not provide their own
.say method.
Finally, this adds two Rakudo::Internals methods for quickly generating
a native str array from a given list, which each element .gist or .Str'd.
:040000 040000 657182be25dc8501e208811c312f852253833ff7 72791ac56c9068129b5fdd7b4a158610cb08affe M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment