I always have this thought. I’m doing it in Rust, so I check if there are negative numbers: if not, use usize. But I’m always terrified there will be an overflow somewhere.
If I were using Kotlin or Java, I might always use BigInteger just out of fear.
That’s a very interesting thought! I was thinking of writing my own Rust data type that would automatically upgrade to big integer, similarly to the int type in Python.
![[2025 Day 5] It always be like that](proxy.php?url=https%3A%2F%2Fprogramming.dev%2Fpictrs%2Fimage%2F761dee7b-4ada-41b7-ba52-0d0749304bf6.jpeg){kind=link}
it all fit in int64 tho, so could be worse
I always have this thought. I’m doing it in Rust, so I check if there are negative numbers: if not, use
usize. But I’m always terrified there will be an overflow somewhere.If I were using Kotlin or Java, I might always use
BigIntegerjust out of fear.That’s a very interesting thought! I was thinking of writing my own Rust data type that would automatically upgrade to big integer, similarly to the int type in Python.
I am doing AOC in Kotlin. Longs are fine. I haven’t encountered a puzzle that required ULong or BigInteger.