You've misinterpreted their warning. They're telling you to use a larger type than normal in order to avoid overflow issues seen with a 32-bit type. Since Python's int is essentially boundless there will never be an overflow issue.
Python 2 has two integer types: int, which is a signed integer whose size equals your machine's word size (but is always at least 32 bits), and long, which is unlimited in size.
Python 3 has only one integer type, which is called int but is equivalent to a Python 2 long.
@SaintWacko yeah same. 'm doing yesterday right now.
I still never got day 16 part 2 working... it's not integer overflow like @MBraedley was thinking I don't believe, since python doesn't care about that.
Going to worry about it after I get caught up
Got some weird ass fucking bug somewhere. Something to do with how I'm parsing tested packets I'm guessing.
You're safe to make an assumption for part 1 that means you don't have to brute-force it, but all you can really do for part 2 is slice obvious failures and brute force the rest.
yeah that's exactly what I did. You just do a range of all velocities which could possibly work based on the target area, and then just simulate all of them.