Nice and efficient too with the set

It is a bad practice, because a value that should be a constant is modified. It would be good if one creates a temporary string that is modified each test (the memory will not overflow from one more mandatory variable). In conclussion, very good solution with poor execution.

nice

Tip: Read the notes in the "Modulo check confirmation example" very carefully. There is a bit of important information there that occurs nowhere else in the description.

bad practice

Handy and readable.

Perfect example to learn "loop for" inside join method

if he used const that makes him can't erase

I know, but it's one of the most efficient methods

python new test frameworks

This code is more like english

It's bad practice to remove them. It's relying on the tests to include them instead, which leaves these solutions prone to being automatically invalidated in the future if the tests change and their solutions don't compile anymore. The line or two saved by omitting them isn't worth that risk, so you're doing good by keeping them in

why theres no #include
i tried it without the lib but dosnt work for me

Very readable and logical. Oh, this language design...