As a follow up to Shortest terminating program whose output size exceeds Graham's number and Golf a number bigger than TREE(3), I present a new challenge.

Loader's number is a very large number, that is kind of hard to explain (since it was itself the result of a code golfing exercise with a flexible goal). There is a definition and explanation here, but for the purposes of self-containment, I will attempt to explain it later in this post as well.

The algorithm Ralph Loader used produces one of the largest numbers of any (computable) algorithm ever written! Indeed, Loader's number is the largest "computable" number on the Googology Wiki. (By "computable" number, they mean a number defined in terms of a computation.) That means that if answer produces a number larger than Loader's number in an interesting way (i.e. not just Loader's number+1), you could go down in Googology history! That being said, programs that produce something like Loader's number+1 are definitely valid answers and contenders to this question; just don't expect any fame.

Your job is to create a terminating program that produces a number larger than Loader's number. This is , so the shortest program wins!

  • You aren't allowed to take input.
  • Your program must eventually terminate deterministically but you can assume the machine has infinite memory.
  • You may assume your language's number type can hold any finite value but need to explain how this exactly works in your language (ex: does a float have infinite precision?)
    • Infinities are not allowed as output.
    • Underflow of a number type throws an exception. It does not wrap around.
  • You need to provide an explanation of why your number is so big and an ungolfed version of your code to check if your solution is valid (since there is no computer with enough memory to store Loader's number).

So here is an explanation of Loader's number. See http://googology.wikia.com/wiki/Loader%27s_number and the links therein for more precise details. In particular, it contains a program that produces Loader's number exactly (by definition).

The calculus of constructions is essentially a programming language with very particular properties.

First of all, every syntactically valid program terminates. There are no infinite loops. This will be very useful, because it means that if we run an arbitrary calculus of constructions program, our program will not get stuck. The problem is that this implies the calculus of constructions is not Turing complete.

Second of all, among non-Turing complete languages, it is one of the most powerful. Essentially, if you can prove that a Turing machine will halt on every input, you can program a function in the calculus of constructions that will simulate it. (This does not make it turing complete, because there are halting turing machines that you can not prove are halting.)

Loader's number is essentially a busy beaver number for the calculus of constructions, which is possible to compute since all coc programs terminate.

In particular, loader.c defines a function called D. Approximately, D(x) iterates over all bit-strings less than x, interprets them as a coc programs, runs the syntactically valid ones, and concatenates the results (which will also be bitstrings). It returns this concatenation.

Loader's number is D(D(D(D(D(99))))).

A more readable copy of the code from the googolology wiki

int r, a;

P(y,x){return y- ~y<<x;}

Z(x){return r = x % 2 ? 0 : 1 + Z (x / 2 );}

L(x){return x/2 >> Z(x);}

   int f = L(t);         
   int x = r;
   return f-2 ? f>2 ? f-v ? t-(f>v)*c : y : P(f,P(S(v,y,c,L(x)), S(v+2,t=S(4,13,-4,y),c,Z(x)))) : A(S(v,y,c,L(x)),S(v,y,c,Z(x)));

A(y,x){return L(y)-1 ? 5<<P(y,x) : S(4,x,4,Z(r));}

   int f;
   int d;
   int c=0;
   int t=7;
   int u=14;
      d = L(L(D(x))),
      f = L(r),
      x = L(r),
      c - r||(L(u)||L(r)-f||(x/=2)%2&&(u=S(4,d,4, r),t=A(t,d)),f/2&(x/=2)%2&&(c=P(d,c),t=S(4,13,-4,t),u=S(4,13,-4,u))),
    return a = P( P( t, P( u, P( x, c)) ),a);

main(){return D(D(D(D(D(99)))));}
  • 2
    \$\begingroup\$ You know Googology Wiki? I'm MilkyWay90 there! \$\endgroup\$
    – MilkyWay90
    Commented Dec 3, 2018 at 23:39
  • 2
    \$\begingroup\$ @MilkyWay90 oh, cool. \$\endgroup\$ Commented Dec 3, 2018 at 23:57
  • 12
    \$\begingroup\$ I would advise against downvoting this for similarity to the TREE(3) question: Loader's number is so much larger than TREE(3) that new and interesting approaches are required. \$\endgroup\$
    – lirtosiast
    Commented Dec 4, 2018 at 1:00
  • 4
    \$\begingroup\$ @fəˈnɛtɪk Well, printing Loader's number + 1 is still interesting from a code golf perspective (for example, can you beat the original 512 bytes?) There are also some natural generalizations of loader's number that might be easier to implement (for example, using ZFC instead of CoC). Also, Greedy clique sequences or finite promise games could be used. \$\endgroup\$ Commented Dec 4, 2018 at 3:24
  • 3
    \$\begingroup\$ Unfortunately, as I don't understand the construction of Loader's number and there does not seem to be known upper bounds in terms of the fast growing hierarchy, I cannot give any good answers here. I believe that most answers will be either extensions of Loader's number or things such as the greedy clique sequences and finite promise games... \$\endgroup\$ Commented Dec 4, 2018 at 12:33

6 Answers 6


JavaScript, D6(9) (508 501 495 492 487 485 481 478 456 452 447 bytes)

_="P.x-~x<<c,Z.r=x&1?0:1+ZC/2$L.x/2>>ZC$S='u,f=6u$d=rJf-2?f>2?f-x?u-(f>x)*c:t:@f,@EC+2K,IZ(d;;:A(E'Z(d;$A.6x)-1?5<<P!):BK,Z(rMD=!=0,H7,N14J_=C&&DC-1$ 1;?(d=66DC;$f=6r$x=6r$c-r||(6u)||6r)-f|| NB,d,r$HA(t,dMfGdK$HIN#u;$c&& H@~u&2| N1<<@6c$uM@6c$tMc=r$uGtK$NIH9$D'u;:@@t,@u,P!;$_$FFF9;;; C>>=1)%2&&(!CK#B-8,13,$),'!,t,.=!J6L(;))@P(BS(4,4C(xES'6dMSFD(D(G/2& c=@Ht=I#t$J)=>K,cM)$Nu=";for($ of"NMKJIHGFECB@;6.'$#! ")with(_.split($))_=join(pop());eval(_)

This is an encoded code.

_="P.x-~x<<c,Z.r=x&1?0:1+ZC/2$L.x/2>>ZC$S='u,f=6u$d=rJf-2?f>2?f-x?u-(f>x)*c:t:@f,@EC+2K,IZ(d;;:A(E'Z(d;$A.6x)-1?5<<P!):BK,Z(rMD=!=0,H7,N14J_=C&&DC-1$ 1;?(d=66DC;$f=6r$x=6r$c-r||(6u)||6r)-f|| NB,d,r$HA(t,dMfGdK$HIN#u;$c&& H@~u&2| N1<<@6c$uM@6c$tMc=r$uGtK$NIH9$D'u;:@@t,@u,P!;$_$FFF9;;; C>>=1)%2&&(!CK#B-8,13,$),'!,t,.=!J6L(;))@P(BS(4,4C(xES'6dMSFD(D(G/2& c=@Ht=I#t$J)=>K,cM)$Nu="; //encoded code
for($ of"NMKJIHGFECB@;6.'$#! ")with(_.split($))_=join(pop()); //decoding
eval(_) //Evaluation of the string

Decoded code:

// We also have _ equal to the code itself.

The logic is the same as the original loader.c, but few non-critical modifications are made to compress the code better.

In this, it is assumed to be:

  • Infinite call stack
  • Infinite memory
  • Infinite precision Number
  • Infinite magnitude Number
  • Bitshift and bitwise operators work on infinite bit integers instead of 53 bits. Bitwise negation still negates the sign bit.

Encoding/Decoding algorithm:

The encoding is done as follows:

  • Take a repeated string, call it S.
  • Replace all S in the code to a key K.
  • Put K and S at the end.
  • Make a list of keys, and also put decoding algorithm so the code actually runs.

The decoding algorithm:

  • Take list of keys.
  • Take the earliest key K.
  • Split the string for each K.
  • Since last of the array is what to replace K S, pop it, and replace all K by joining the array with the popped value S.

The compression was done with this code.

(d=String.fromCharCode)((c=a.charCodeAt())>>8)+d(c&255)).join``.slice(1)) ``` This code will take the 16bit string as a, converts it to 8bit string with same binary(BE), and `eval` it. The decoded code is the encoded code above. -->

Proof that D6(9)>D5(99)

For this, we would compare D(0) and 99. We find that D(0) is equal to 8646911284551352321 (note that in a normal environment without modifications we won't get a correct result because the higher bits are truncated). So, D(0)>99, and since D is strictly increasing, D6(9)>D6(0)>D5(99).

  • 508B->501B, -7B
    • -1B for... I don't know why. I did change D(D(D(D(D(99))))) to D(D(D(D(D(D(9)))))). Also that shuffled the letters.
    • -6B for re-adding &&(1) for D(x)'s loop condition.
  • 501B->495B, -6B
    • Fixed most /2s to >>1s because Number
    • 6 bytes saved from somewhere
    • You can see my attempt in this update here
  • 495->492B, -3B
    • By changing the decoder from for...in to for...of.
  • 492->487B, -5B
    • Removing unnecessary assignments
    • Changing argument names
  • 487->485B, -2B
    • 1 byte from using eval for D, removing return.
    • 1 byte compression combining the closing parentheses to a comma.
  • 485->481B, -4B
    • By compressing different substrings.
  • 481->478B, -3B
    • Removed unnecessary variable assignment.
  • 478->456B, -22B
    • You can find me posting updates at Googology Server! (Discord).
    • 2 bytes from changing from D6(9) to D6(0).
    • 1 byte from making D recursive instead of using a loop.
    • 7 bytes from making f and d in D global and not declaring them. It works since they are reassigned every time going through the loop, and D is not called between the assignment and the next iteration.
    • 2 bytes from removing assignment to r. They will be assigned before use.
    • 1 byte from removing an unnecessary assignment corresponding here in the original code. It no longer saved bytes.
    • 1 byte from fixing a typo. I still don't know how it appeared.
    • 2 bytes from swapping the second and the third variable of S. I checked and it should work fine.
    • 1 byte from changing instances of S(4,-4,13, to S(4,4-8,13,.
    • 2 bytes from adding unused variables y to Z and L.
    • 1 byte from changing Z.
    • 2 bytes from reusing _ as the accumulator. It starts out as a String containing the decoded code, and in such a case, it acts as 0 in bitwise operators. Also changed back to D6(9) for good measure.
  • 456->452B -4B
    • Changed the 1-argument and 2-arguments functions' argument names to (x,c).
  • 452->447B -5B
    • Renamed the arguments of S to match D's.

Python, q^15(2) = q^13(5), 319 bytes

This is my first time submitting a program to code golf, but certainly not my first time implementing or inventing a large number. I probably won't go down in googology history for this. Anyway, here is my program, the explanation comes later:

_="78b/:!if b==1:&(a+1)%c!9&s(8b-1/,s(81///\n7f(a):!m=[]*True:!#for x in range(65536):!##if a(x)==a(x+k): break!##9 pass'p = 4x:f(4y:s(1,y,x))\n7q(a):*p(k)<2^a:'k = $$$$$2...!\n##    $q(q(q('!#k+=1!&k\n&return *!k=0!while .)))))/,c)4lambda 7def 8s(a,9else:"
for Y in"9874/.*&'$#!":_=_.split(Y);_=_.pop().join(_)

I compressed this code using the same tool which Naruyoko used, here. Here is the uncompressed form:

def s(a,b,c):
    if b==1:return (a+1)%c
    else:return s(s(a,b-1,c),s(s(a,1,c),c),c)
def f(a):
    while True:
        for x in range(65536):
            if a(x)==a(x+k): break
            else: pass
    return k
p = lambda x:f(lambda y:s(1,y,x))
def q(a):
    while p(k)<2^a:
    return k
k = q(q(q(q(q(q(q(q(q(q(q(q(q(q(q(2)))))))))))))))


I had a hard time choosing what to use. I was originally planning to implement my LINEAR(k) function, which I might do another time, but I didn't know if it would produce large enough numbers, and it would be hard to implement, so my next choice was greedy clique sequences, but those didn't work either, so I just ended up using Laver tables.

So, how do Laver tables work? Well the size-n Laver table is a binary operator ab, with the following rules: a0=0, a1=a+1 mod n and ab=(a(b-1))(a1) for b>1. p(n) is defined as the period of the function 1a, which is quite slow-growing.

The first few values of p(n) are 1,1,2,4,4,8,8,8,8,16,16,16,16,... Then q(n) is the least integer so that p(q(n)) is greater than or equal to 2^n. This is very fast-growing, and its totality can only be proven in ZFC+I3, so one could approximate it to f_PTO(ZFC+I3)(n) in FGH, although this doesn't work since there is no system of fundamental sequences associated to PTO(ZFC+I3).

The first few values of q(n) are 0,2,3,5,9. q(5) is approximated to Ack(9,Ack(8,Ack(8,255))) using the Ackermann function, and q(6) is believed to be greater than Graham's number!

So, now that we know how Laver tables work, how does my code work? Well, s(a,b,c) denotes the operator ab where n=c, then the function f(a) uses complex while loops to find the period of the given function a.

p is represented by the lambda which returns f(lambda y:s(1,y,x)), i.e. the period of s(1,y,x) where x is the input to p. q then just uses for loops to find the least integer k s.t. p(k) => 2^a.

My code then returns q^13(5), which has been proven to be greater than f_w(f_w+1(5)); note that this was for q^13(1) but q is strictly increasing so this also acts as a lower bound for q^13(5). This lower bound however is a severe understatement, since, as I mentioned earlier, q(n) cannot be proven total in ZFC while f_w(f_w+1(5)) can be by FAR.

Similarly, this code should return a number greater than Loader's number since, although sadly there is no proof, Loader's function is commonly believed to be provably total in ZFC; I do note however that just because a function which is provably total in a stronger theory doesn't mean that it will eventually dominate the one provably total in the weaker theory. It is usually the case though. So, all said, I WIN!!!

Edit: I lose because the code is completely broken and I can't fix it...

  • \$\begingroup\$ Welcome to the site. \$\endgroup\$
    – Wheat Wizard
    Commented Nov 20, 2021 at 13:22
  • \$\begingroup\$ As written, your for loop is dead code—it either breaks out of itself or runs to completion, but either way it has no effect on the surrounding code. There is no way for the while True loop to terminate. How is this function intended to work, and what’s the purpose of the constant 65536? \$\endgroup\$ Commented Nov 20, 2021 at 19:23
  • \$\begingroup\$ I'm not that good with loops and breaks and stuff. >What's the purpose of the constant 65536? I chose it to be big enough, to ensure that in something like 2,4,2,6,3,2,4,2,6,3 it doesn't return 2 since the 2 repeats after 2 spaces, instead it should return 5. > As written, your for loop is dead code Sorry, I will fix it tomorrow. \$\endgroup\$
    – Binary198
    Commented Nov 20, 2021 at 21:11
  • 2
    \$\begingroup\$ I was inspired by this answer to post a (hopefully working) implementation of this function as another answer. \$\endgroup\$
    – benrg
    Commented Apr 15, 2022 at 6:15
  • 1
    \$\begingroup\$ It's currently not known if q(n) can be proven total in ZFC or not, just known that it can be proven total in ZFC+I3 \$\endgroup\$
    – C7X
    Commented Jun 2, 2022 at 21:12

Python, q15(2), 192 bytes

def q(k,c=0,n=0):
 while c*2<1<<k:
  n+=1;*x,=map(s:=lambda b,a=1:s(a,s(b-1,a))if a*b else(a-~b)%c,range(c:=1<<n))
  while x[:c]==x[-c:]:x=x[:c];c>>=1
 return n

See Binary198's answer for the definition of q and an argument that q15(2) is large enough. If the argument is correct, then this is an impressively concise way to beat Loader's number. Unfortunately their implementation is broken.

This is my attempt at reasonably well golfed code that, I think, actually works. At least, it correctly computes values of q up to q(3)=5. (If you want to test that, you should wrap the definition of s in functools.lru_cache(None)(...).) Computing q(4)=9 may be possible, but will need a lot of stack space.

s(b,a) computes row a, column b+1 of the Laver table of size c, using 0...c-1 as the representatives of Z/cZ instead of the usual (for these tables) 1...c. The period-finding code uses the fact that the period can only be a power of 2. Other than that, there are only standard golfing tricks here.

I deliberately computed the same value as Binary198's answer, though it could be made larger at no cost, because I'm not trying to compete on size; I just wanted a working implementation of this interesting function (for some definition of "working").

  • \$\begingroup\$ q() is not known to grow faster than Loader's D(). It's not even known whether q(5) exists. If it does, then 2^q(5)-1 can be computed in only 27 bytes, as shown in codegolf.stackexchange.com/questions/79620/… and 2^q(17)-1 in a few bits more. \$\endgroup\$
    – John Tromp
    Commented May 10 at 10:36

Python, 498 bytes, ???

I don't know how large this program would get.

Okay, I've had a few failed attempts on this, but I think I've got it this time. First, the code:

from itertools import product as X
def R(n):
    while C[0]:
        for m in r(V[0]):P(m,n)
    return sum(V)
def P(m,n,B=0,T=0):
    if m==len(V):V.append(0)
    for M in X(*[L(X(*[L(X(c,c,[-1,0,1]))]*k))]*k):
        while d:
            if u>sum(V):u=d=0
    if T>V[m]:C[0]=V[m]=T;C[1]=min(C[1],m+1)
    if B>C[0]:V[m]+=1;P(m,n,1)


This function simulates all Turing machines with n states and n colours for a number of steps (initially 9), then sums the number of steps that it took for any machine that halted to halt, storing that value as the number of steps to take on the next iteration. It keeps doing this until it reaches a steady state.

We don't just look at machines that have n states and colours, but also n+1, n+2, up to n+V[0], where V[0] is the sum of the halting times for the machines with n states and colours.

So far, I've just described a function which is polynomial at best. Notably, it grows slower than the busy beaver function on these Turing machines. Thus, we can be confident that there is at least one machine of size n which halts but we have not yet found. So we search for that one (this function is undefined on inputs which are too small).

Once we find it, we continue on as we were. We'll reach another steady state. This time, we can't be confident that there is another halting Turing machine of size n, but as BB(n+1)>F(BB(n)) for any reasonable polynomial function F (which this is), we can be confident that there is a halting Turing machine of size n+1 which we have not found. If we then find a halting machine of size n, we know that we can perform this step on n+1 again.

We repeat this process until we've attempted this on every size of machine we're looking at (from n to n+V[0]), and thus can no longer be confident that there is a machine that halts of those sizes that we have not seen.

While this number is certainly less than BB(n), I'm not sure how one would go about determining just how big it is. The guarantee that it halts is basically "BB(n) grows much faster than this does". I'm fairly confident that's a safe assumption for values of R(n) greater than, say, R(5).

Here's a less golfed version with comments:

from itertools import product as X
 # C[0] is 1 or 0 representing a change, so keep looping
 # C[1] is the next machine that needs to search.
 # V[x] is the total steps taken by the machine with n+x colours and states
def R(n):
    while C[0]:
        # Run each set of machines sum(V) steps.
        for m in range(V[0]):P(m,n)
        # Run machine set C[1] sum(V) steps, then run it until one more machine stops.
        if C[0]<1 and C[1]<len(V):P(C[1],n,1)
    return sum(V)
 # Run one set of machines with m+n colours and states.
def P(m,n,B=0):
    if m==len(V):V.append(0)
    # Start our total at 0
    # For each machine in the set...
    for M in G(m+n):
        # Step count u starts at 0
        # The tape t starts empty
        # Position p starts at 1
        # State s starts at 1
        # Direction d starts at 1.  These are all 1 because it's shorter and we use d=0 as break
        while d:
            if u>sum(V):u=d=0
    # If the total is greater than the last time we ran this set, increase it and note there's been a change
    if T>V[m]:
        if m<C[1]:C[1]=m+1
    # If we're running it until there's a change, increment V[m] and try again.
    if B>C[0]:V[m]+=1;P(m,n,1)
 # Generate all the machines of appropriate size.
def G(k):
    # List of colours
    # List of options for a single state/colour combination - new state, colour written, direction moved (0 being halt)
    # List of options for one state
    # List of options for all states
    return L(X(*[S]*k))
for i in range(R(r)):
    # Reset C[0], as we need to be able to run again.  C[1] will get reset in P().

Actually, it occurs to me that there's no reason why (in principle) we can know that R(n) < BB(n) (when BB(n) is defined to be on Turing machines with n colours and states). Determining exactly how big R(n) is is related to a limited version of the halting problem, as it isn't guaranteed that $$BB(n)*2^{n*2^{3n^2}}<BB(n+1)$$ That's the limit on how quickly R(n) grows without the "look for the next terminating machine" step. I think it's a pretty safe assumption, though, that it's true with n>5 or so.

while we can know that R(n) halts on big enough inputs, it's certainly possible that the result is in every case larger than BB(n). Proving such (if true) would be equivalent to the halting problem, of course.

  • \$\begingroup\$ I'm looking at the golfed code and some stuff isn't making sense. if(C[0]sum(V): looks like a typo -- it's not syntactically valid. P and T are undefined. L and X are defined but not used. \$\endgroup\$
    – xnor
    Commented Feb 14, 2020 at 20:09
  • \$\begingroup\$ @xnor There was an edit fixing formatting; it caused a bunch of stuff to disappear because < was causing issues. I've corrected it now. \$\endgroup\$ Commented Feb 14, 2020 at 20:15
  • 1
    \$\begingroup\$ I tried to fix it. Let me know if there's trouble. Code blocks (with Ctrl+K) respect code formatting better than code tags. \$\endgroup\$
    – xnor
    Commented Feb 14, 2020 at 20:24
  • 1
    \$\begingroup\$ It looks like z=9e9 ends up in a range, which only accepts integers, not integer-valued floats. So I think you need something like 9**9 or whatever is big enough. \$\endgroup\$
    – xnor
    Commented Feb 14, 2020 at 20:26
  • \$\begingroup\$ @xnor and Spitemaster mea culpa. I just put in the tags and didn't even check the output. Lazy editing on a Friday afternoon. That'll teach me to ship code on a Friday. \$\endgroup\$
    – Giuseppe
    Commented Feb 17, 2020 at 20:53

Ruby, D6(9) (553 544 535 516 511 507 bytes)

_='a=r=0;P"x-~x<<y};Z"r=x%2B1?0M1+J/2FL"x/2>>JFS=->vEt{f=L(t);x=r;fB2?A*EJ6Mf>2?fBv ?yMf>v ?t-cMtM@f,P*+2,#y8c,J6FA"Cx]B1?Ky,4,Z[r]]M5<<@x,yFD"f=d=c=0;t=7;O14;while[xIHx-18.>0][1];d=CCHx6;f=N;x=N;cBr&&[Cu]B0&&NBf&&.I[OKd,4,rQA[t,d]8fGd,cQ#t8O#u6;cI.&&[t=@~u&2|.I(O1<<@Cc8u]),@Cc8t]8c=r];uGt,c8O#tQ9];end;a=@@t,@u,@x,c6,aF$><<HHHHHH966"=->x,y=0{#K13,-4,*[S[vECx]8S[v.(x/=2)%26]]]8],@P[B==CL[E,y,c,F]};G/2&.I[c=@HD[IB0||JZ[xKS[4,M: NCr]Ou=Q8t=';'QONMKJIHGFECB@86.*#"'.each_char{|y|*_,y=_.split y;_=_*y};eval _

This is an encoded code. Extracted:

a=r=0;P=->x,y=0{x-~x<<y};Z=->x,y=0{r=x%2==1?0: 1+Z[x/2]};L=->x,y=0{x/2>>Z[x]};S=->v,y,c,t{f=L(t);x=r;f==2?A[S[v,y,c,L[x]],S[v,y,c,Z[x]]]: f>2?f==v ?y: f>v ?t-c: t: P[f,P[S[v,y,c,L[x]],S[v+2,S[4,13,-4,y],c,Z[x]]]]};A=->x,y=0{L[x]==1?S[4,y,4,Z[r]]: 5<<P[x,y]};D=->x,y=0{f=d=c=0;t=7;u=14;while[x==0||D[x-1],(x/=2)%2>0][1];d=L[L[D[x]]];f=L[r];x=L[r];c==r&&[L[u]==0&&L[r]==f&&(x/=2)%2==0||[u=S[4,d,4,r],t=A[t,d]],f/2&(x/=2)%2==0||[c=P[d,c],t=S[4,13,-4,t],u=S[4,13,-4,u]]];c==0||(x/=2)%2&&[t=P[~u&2|(x/=2)%2==0||(u=1<<P[L[c],u]),P[L[c],t]],c=r];u/2&(x/=2)%2==0||[c=P[t,c],u=S[4,13,-4,t],t=9];end;a=P[P[t,P[u,P[x,c]]],a]};$><<D[D[D[D[D[D[9]]]]]]

This code is Loader's Number with D6(9) instead.

In this, it is assumed to be:

  • Infinite call stack
  • Infinite memory

This is basically a port of my JavaScript answer and Python 3 answer. For more details, check those.

The compression was done with this.

I am a beginner at Ruby, so maybe under 512 is possible, but I doubt it.

  • 553->544B, -9B
    • Added 3 bytes from fixing a formatting error.
    • 5 bytes from removing an unused print.
    • 4 bytes from changing expression t-(f>v ?1: 0)*c to f>v ?t-c: t
    • 1 byte from removing an unnecessary assignment to t.
    • 2 bytes from removing an assignment to r.
  • 544->535B, -9B
    • Improved the decoder.
  • 535->516B, -19B
    • 17 bytes from changing functions to lambda expressions.
    • 1 byte each from removing parenthesis from split and eval.
    • Thanks @Dom Hastings!
  • 516->511B, -5B
    • Use a and r declared globally, instead of $a and $a.
  • 511->507B, -4B
    • Change all 1 and 2 argument functions' arguments to x,y=0.
  • 1
    \$\begingroup\$ Hey, nice answer! I think you can save a few bytes dropping parens from eval, split, etc, and in the compressed string any calls that are before a ; or ] could probably have parens removed too. Even D D D D D D 9 should work. Not sure if that'll help get closer to 512... \$\endgroup\$ Commented Jul 29, 2021 at 8:01

Python 3, D^6(9) (608 600 599 597 591 583 573 572 bytes)

_="a=0@PJ$x-~x<<c@ZJr=0'C?1+YxKO$r@LJ$xK+Yx)@SBu!f,d=FuQr#$A(RBYdE)'f==2?If,IR(x+2U,/tQYdEE'f<2?u-(f>x)*c'f-x?t@AJ$5<<P.)'Fx)-1?MU,YrE@D.=0,t=7,u=14!Hx:Nx-1O6H~CXa=IIt,Iu,P.EQaO $a#d,f,x=FFNxEQFrQFrOHc-r:#'not(Fu)or(Fr)-fEG'C:u=M,d,rTA(t,dO'fKG'WdUT/tVuOHcX6'CG q=~u&2|C# 'q:u=1<<IFuQuO  tU=Iu'q?q,IFcQtE,r#6HuK&WtUVtT9#$DBu)\nprint(NNNNNN9EEE)!):#global r,a##\n $return ' H.(xU/M-8,13,6x=xK#? else @\ndef B.,t,Cx%2E))FL(GX 6 Hif IP(J.=0!K>>1MS(4,4ND(O)#Q),RSBFdE,ST);t=U,cV);u=/WC:c=IX:# YZ("
for Y in"YXWVUTRQONMKJIHGFECB@?6/.'$#!":_=_.split(Y);_=_.pop().join(_)

This is an encoded code. Extracted:

def P(x,c=0):
 global r,a
 return x-~x<<c
def Z(x,c=0):
 global r,a
 r=0 if x%2 else 1+Z(x>>1)
 return r
def L(x,c=0):
 global r,a
 return x>>1+Z(x)
def S(x,c,t,u):
 global r,a
 return A(S(x,c,t,L(d)),S(x,c,t,Z(d))) if f==2 else P(f,P(S(x,c,t,L(d)),S(x+2,c,S(4,4-8,13,t),Z(d)))) if f<2 else u-(f>x)*c if f-x else t
def A(x,c=0):
 global r,a
 return 5<<P(x,c) if L(x)-1 else S(4,4,c,Z(r))
def D(x,c=0,t=7,u=14):
 global r,a
 if x:D(x-1)
 if ~x%2:
  return a
 if c-r:
  if not(L(u)or(L(r)-f)):
   if x%2:u=S(4,4,d,r);t=A(t,d)
  if f>>1:
   if x%2:c=P(d,c);t=S(4,4-8,13,t);u=S(4,4-8,13,u)
 if c:
  if x%2:
   if q:u=1<<P(L(u),u)
   t,c=P(u if q else q,P(L(c),t)),r
 if u>>1&x%2:c=P(t,c);u=S(4,4-8,13,t);t=9
 return D(x,c,t,u)

In this, it is assumed to be:

  • Infinite call stack
  • Infinite memory

This is basically a port of my JavaScript answer. For more details, check that one.

The compression was done with this.

I am not very knowledgeable in Python, so there are certainly places to save bytes. I think sub-600 is possible. sub-600 has been proven.

  • 608->600B, -8B
    • Grouped some assignments
    • Reversed conditions of S to reduce parenthesis
  • 600->599B, -1B
    • Changing u/2 in the third last line of the definition of D to u>>1, saving a byte from compressing it to a character with other >>1s.
  • 599->597B, -2B
    • 2 bytes from removing assignment to r.
  • 597->591B, -6B
    • Made D recursive.
    • Removed the unnecessary assignments to d, f, and c. Making D recursive allows this to be completely removed and save more bytes whereas keeping it in a loop would have still needed an assignment to c.
  • 591->583B, -8B
    • Changed the 1-argument and 2-arguments functions' arguments to (x,c=0).
    • Added global r,a to every function.
    • Swapped the second and the third of S.
    • Changed the instances of S(4,-4,13, to S(4,4-8,13,.
    • Fixed the compression algorithm (specifically displaying) so it actually works now.
  • 583->573B, -10B
    • Replaces q and u with u if q else q and that somehow saved 10 bytes.
  • 573->572B, -1B
    • Renamed the arguments of S to match D's.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.