omg you're such a beast

ahah when two Shifu meet

try c++, it always looks classy xD

this is a German supermarket, so no human factor is involved xD

thank you! I had fun with it! You should make MORE katas!

xD

omg super-clever, i kneel bevor thee

thanks for the response!

the examples, the sample tests. If the Task contains Examples, then one can RELY on these examples - and here they perfectly match each other. If the Task and Examples are going along with Sample Tests (which are no different from each other) - it looks like there's no other way to present the task:
(alpha)-(zeroes)-(numbers)

..aaand when everything is planned and implemented, here we go -
(alphanum)-(zeroes)-(numbers). Needless to say, it ruined my algorithm. I'm not advocating for revealing the "hidden test-cases", but it's UNFARE to make the "hidden test-cases" more narrow than thetask

thank you.

i didn't expect an extended test input "fo99obar100". The given test cases look like:
do_test("foobar000", "foobar001");
do_test("foo", "foo1");
do_test("foobar001", "foobar002");
do_test("foobar99", "foobar100");
do_test("foobar099", "foobar100");
do_test("", "1");
do_test("1", "2");

no way one can infere such a test case after seeing these Examples.

what's the reason (just curious) //c++

and yet another incomplete task description. Why do the extended test cases contain something that isn't mentioned in the Instructions? Otherwise could be great kata

beautiful

we need more code for the god of code

ahah true

too sophisticated for me at the moment :)