Also forgot that. ✅fixed

Totally my bad. Should have looked into that a little deeper. TOP = 15 should be fine now since:

Long.MAX_VALUE -> 9223372036854775807
        10**15 -> 1000000000000000

Fixed ✅
TOP is 20 now

I completely overhauled the C test suite. I replaced the reference solution, as it was wrong for several kinds of invalid inputs, e.g. ".1.2.3.4", "1.2.3.4.", etc.

Done in this fork

Fork already approved some time ago.

Added a Haskell fork.

over

Another programming language is not a valid point, because different languages are done with translations, and not by creating new but similar challenges.

Description seems to be not a valid point either, because description can be updated. If you think that the description of the currently existing task is wrong, you can raise an issue and explain the problem.

So basically the only remaining point is the additional condition in the other challenge, which is not present in your challenge. Now the question would be, how different does it make your challenge from the other one? Are they very similar? How are solutions different? Do they differ more significantly than just one additional if, or some small block? If some user solves your challenge first, and the other challenge later, will they feel that they just solved the same problem twice? This would be the most relevant factor to decide whether your challenge is a (close) duplocate or not.

yes, I agree that the essence of the task is the same, but that task is not described according to the rules of Codewars, and there is also an additional condition that I do not have, + the task is in another programming language

Already fixed in this fork

Modified description to have :

Not all strings will contain digits and not all inputs will be string. In those cases, return -1.

Should be clear now.

I merged a fix, can you please verify.

fork

Fork that updates the random tests.