Hey, I really think that you should mention that strings are not the standard way of representing bigintegers, and to speed your code up, you should use an array of unsigned longs instead. I fell too deep into the string bigint rabbit hole before I realised myself.

https://www.codewars.com/kumite/6319e777b80b15c8265ce45c?sel=6319e777b80b15c8265ce45c

NASM translation!

dude what the~

Well, what's the difference? I could do that, and it might make it easier, but if you chose NASM, you shouldn't be expecting it to be easy. Unless there's any other reason, of course.

Hello there! I didn't use cr_assert_str_eq because, well, I didn't know that was a thing. I'll change it right now.

EDIT: Done, it's cr_assert_str_eq now.

Really? Can you check again? It's fine on my side.

You're right; fixed that as well. But I think I'll stick to a vector.

Was only in the sample tests, but it's fixed now.

Yeah, the cret0r is very inactive. Also, random tests for cpp are broken.

The C++ random, and fixed tests are so broken. They need to be fixed. When comparing doubles, you can't use exactly equal to. This is a serious bug. See https://docs.codewars.com/authoring/recipes/floating-point/

Wow, this made me laugh for 2 minutes straight. 'Very unhelpful', more like pathetically useless xD. Anyway, I changed that too. Thanks!

Done, thanks!

I agree, but not 4. It's not a 2, but definitely not a 4 either. 3 is good.

Woah, you actually managed to translate this to assembly? Respect, man.

In C++ I'm getting
Expected: equal to 2 Actual: 2

Um, what? Maybe the test cases don't compare doubles properly?

Almost all of the tests fail this way. Is there any way to fix this? Please? @ankr