Skip to content

Instantly share code, notes, and snippets.

@Whateverable
Created December 6, 2019 13:06
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save Whateverable/6d11563ebb64f275ee5bfd98e4736f5f to your computer and use it in GitHub Desktop.
Save Whateverable/6d11563ebb64f275ee5bfd98e4736f5f to your computer and use it in GitHub Desktop.
bisectable6
old=2015.01 42 .say
Bisecting: 7611 revisions left to test after this (roughly 13 steps)
[f9ed7300fc4c3b8f6b170f2dd80099f3c65fca43] Remove unnecessary stubs
»»»»» Testing f9ed7300fc4c3b8f6b170f2dd80099f3c65fca43
»»»»» Script output:
42
»»»»» 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 7e3d0b8369812635097a0db66ae6e4dec3f92833
»»»»» Script output:
42
»»»»» 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 cac198b55aa6da0c23ebcaaafe38b2382deb82c0
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/BmA1BPDBTy
Two terms in a row
at /tmp/BmA1BPDBTy:1
------> 42⏏ .say
expecting any of:
infix
infix stopper
statement end
statement modifier
statement modifier loop
»»»»» 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 2ec6e14d1a6c5bbfbf2a3c44ccfa84277c1fec33
»»»»» Cannot test this commit. Reason: Commit exists, but an executable could not be built for it
»»»»» Therefore, skipping this revision
»»»»» -------------------------------------------------------------------------
»»»»» Testing c80f75d671833e6fddc80a5d2a3185985edd015f
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/BmA1BPDBTy
Two terms in a row
at /tmp/BmA1BPDBTy:1
------> 42⏏ .say
expecting any of:
infix
infix stopper
statement end
statement modifier
statement modifier loop
»»»»» 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 2f4bfd89d6b845f01eea052eb117b2670cf83e65
»»»»» Script output:
42
»»»»» 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 7b54492b9ab887d6bc7d7e4e5792814ef77fdd21
»»»»» Script output:
42
»»»»» 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 b6247a813bef0863f2c723216886922601742fec
»»»»» Script output:
42
»»»»» 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 e0b56aa5c9607abe7cd29e838970b761580a42ca
»»»»» Script output:
42
»»»»» 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 7116059675fa742312ee995f8ff00d64399c883c
»»»»» Script output:
42
»»»»» 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 5f5cfcfc711804a248ecfadb92dfe13c58848e27
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/BmA1BPDBTy
Two terms in a row
at /tmp/BmA1BPDBTy:1
------> 42⏏ .say
expecting any of:
infix
infix stopper
statement end
statement modifier
statement modifier loop
»»»»» 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 0132b654104259b26a2920fb9a89f545281bb9b3
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/BmA1BPDBTy
Two terms in a row
at /tmp/BmA1BPDBTy:1
------> 42⏏ .say
expecting any of:
infix
infix stopper
statement end
statement modifier
statement modifier loop
»»»»» 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 db0c46e74491479a228f7da5570f5ca99b7618df
»»»»» Script output:
42
»»»»» 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 73836e1a70378b0c56c234e84385159564a0c355
»»»»» Script output:
===SORRY!=== Error while compiling /tmp/BmA1BPDBTy
Two terms in a row
at /tmp/BmA1BPDBTy:1
------> 42⏏ .say
expecting any of:
infix
infix stopper
statement end
statement modifier
statement modifier loop
»»»»» 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 cb25b2f475f31335d77d018474482aceec2c74de
»»»»» Script output:
42
»»»»» 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”
cb25b2f475f31335d77d018474482aceec2c74de is the first new commit
commit cb25b2f475f31335d77d018474482aceec2c74de
Author: TimToady <larry@wall.org>
Date: Sat Sep 26 23:01:22 2015 -0700
Allow infix:<.> if next thing is alphabetic
As much as I mistrust "fluent" programming, we already have an infix:<.=>
operator, so it's not a big stretch to have infix:<.>. We limit it
to actual method names so that we can detect (most) accidental use
of P5's use of . for concatenation. Note that this is a term/infix
distinction now, so .meth where a term is expected still defaults to $_.
Community standards for method cascades will likely ask for whitespace
around infix:<.> to make a visual disinction from the term form, but we
don't enforce that, if for no other reason than to refrain from giving
the fluent programmers something to yammer on about. Basically, I've
decided that the slight possibility for greater confusion is outweighed
by consistency with .= and utility of have a . that can also serve as
a precedence modifier. (Since both .= and . parse leftward with
item assignment precedence, but rightward as a term.)
:040000 040000 be07c9752378c7034bc8d1ab2b34c78903ae1029 b09e45504a167da4e8328131c80bebac71267277 M src
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment