Approved

int to str conversion in Python is comedically slow, I doubt the runner could even stringify the really fuckhuge numbers we get here in time to show them to you. Even if it can you still have the 1.5MB reporter buffer limit to deal with (I'm pretty sure the largest inputs don't even fit within it).

Yes you're right. I just get this error when I print the larger int values. I guess the ints get converted to strings first, and there's a limit on string lengths.

"ValueError: Exceeds the limit (4300) for integer string conversion; use sys.set_int_max_str_digits() to increase the limit"

See above, this occurs when you print the integer value.

Well when we consider that 200 people have, it would appear to be completely unncessary. We can't even work out how on earth using that would help tbh.

In particular I don't think you can solve the problem without a call to this: sys.set_int_max_str_digits()

In what way is it needed? No solutions were invalidated and it was already banned before.

Also, sys being banned is just part of the module forbidder in order to give it some chance of working.

Did you ban sys? It's needed for large ints in Python.

Should probably switch to returning answers mod 1e9+7 or similar. Poor design when most of the runtime is taken up by bigint maths that the user has no control over.

For example, we converted our Scala translation to use Longs instead and it can handle the performance tests in 5ms rather than 4000ms.

Scala translation

Fixed, module forbidder also updated.

Fixed.

The Python test bounds were also a lie, it only ever went up to 1_000_000.

Python new test framework required.

Haskell and JS:

• Description does not specify random test bounds.