Yeah, it has been a while since I made this, looking back at it right now and I'm not very happy with the way the code turned out. The code is interesting, show some cool tricks, but it is not a good answer.

Arbitrary precision is fine and all, but the best method is to just avoid the mess of floating point numbers using formulas.
But this is insanely clever!

I just tried doing this and had the same problem :o
Very glad, that Durudo posted the correct way

I really like this solution. Clean and readable.

THIS IS WHAT I WAS SEARCHING FOR BECAUSE OF ROUNDING ERRORS.

for example in python sqrt(6331294295132068901) = sqrt(6331294295132068900) which obviously isnt the same!!!!!

Thank you - learned something new :)))

int num = min + 37 - (min % 63);

num = (num >= min) ? num : num + 63;

What's the logic behind this?

Can you explain this to me, please?

Can anyone explain this solution step by step? Seems too strange to me

"res" is in the stack, you cannot return it because at some point - after the return of the function - this memory will be released.

Yes, actually we have a problem right here. Just checked and std::string does not terminates in NULL, I thought that was the case.

Yes, actually we have a problem right here. Just checked and std::string does not terminates in NULL, I thought that was the case.

Yes, index is out of range and can lead to undefined behavoir. Should really be checking for i>0 and i<fight.size()-1