There is a test where one of input strings contain some leading zeroes. It's no big deal to make a workaround, but it leads to inconsistency:

1. Description says we can expect a two strings with number. Not everyone will consider string with digits and leading zeroes a valid number. If we not consider this a number, we need to remove that test.
2. If we consider this a number, then answer (sum of two numbers is undoubtedly a number) with leading zeroes should be accepted or necessity of trimming leading zeroes must be written explicitly in description.

This kata is a subject to deduplication process here: https://github.com/codewars/content-issues/issues/206.
Please join the discussion to help us identify duplicate kata and retire them.

Rust translation finished.

AFAIK, there is no readily available BigInt in Rust.

Added anti-cheat.

Please, this Kata blocks BigInt, but it doesn't say that BigInt is not allowed. Does anyone know how I can use BigInt without BigInt?

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.

Hello. I am try solve this kata in C language. Fixed tests passed, but random tests throw "Test Crashed Caught unexpected signal: 6". Help me please.
PS: Sorry for mistakes in my question, I am badly know English...

If the kata has further requirements (i.e. anti-cheat) this should be stated in the description

C# fork disabled BigInteger

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

NASM translation!

Let's change the idea of the text. For example, let there be a mailing manager

Add a conditional comment for javascript: BigInt is disabled/not available

Should have added that BIG INT libraries are not allowed, otherwise this kata has no point.
Everyone is just using a library, ignoring the actual point of this kata.