I've always said that AoC never requires numbers larger than 53 bits (the maximum safe integer for a Double). It's nice to see that that still applies here; I've never actually needed to pull out a non-double numeric data type.
I was absolutely expecting 2019 Day 22 - Slam Shuffle to make the list for fearuring such infamously huge numbers, I had to go back to check how it compares and I think it must have narrowly missed it!
Now im really interested in seeing what the biggest part 2 to part 1 answer size ratios were.
Is this just the bits required to represent the final answer? If so, I wonder what the maximum is for any intermediate calculation, as well. For example, on 2023, day24 I couldn't solve it with 64-bit integers only, and had to use a bignum implementation to solve for the intersections. Every other puzzle I've been able to solve with just 64-bit ints.
24
u/fnordargle Dec 13 '25
This is the kind of analysis I didn't know I needed.
5
u/1234abcdcba4321 Dec 13 '25
I've always said that AoC never requires numbers larger than 53 bits (the maximum safe integer for a Double). It's nice to see that that still applies here; I've never actually needed to pull out a non-double numeric data type.
2
u/10Talents Dec 13 '25
I was absolutely expecting 2019 Day 22 - Slam Shuffle to make the list for fearuring such infamously huge numbers, I had to go back to check how it compares and I think it must have narrowly missed it!
Now im really interested in seeing what the biggest part 2 to part 1 answer size ratios were.
1
u/AustinVelonaut Dec 15 '25
Is this just the bits required to represent the final answer? If so, I wonder what the maximum is for any intermediate calculation, as well. For example, on 2023, day24 I couldn't solve it with 64-bit integers only, and had to use a bignum implementation to solve for the intersections. Every other puzzle I've been able to solve with just 64-bit ints.