git blame "you knew it was wrong, but you did it anyways"

eh, hash it with a set and find the length

if you find you need to care about the size of your int (just kidding: it always matters..), it's normally best to explicitly use a type with a size like uint32_t

Quick Comments

• Welcome to SO! What exactly have you tried so far? We're much more here to help with specific questions of the form "I tried X, but it did not do what I expect and instead resulted in an error!" accompanied by a Minimal, Complete, and Verifiable example
• XY Problem
• https://meta.stackoverflow.com/questions/260648/stack-overflow-question-checklist
• https://meta.stackoverflow.com/questions/285551/why-not-upload-images-of-code-errors-when-asking-a-question
• check out pdb - The Python Debugger to debug small programs python3 -m pdb myscript.py .. use b to set a breakpoint (so you can inspect your program there), c to run up to that point (continue), and ? to explore commands .. this will allow you to inspect the live state of your program wherever you breakpoint or continue to