It's a good implementation, but by nature converting a number into a string is much more complicated than a simple while loop which runs a dozen or so times.

There are a lot of restrictions that should be applied so user code won't just use Python classes to implement said class system. At least the user should not be able to

• use class syntax (for obvious reasons)
• eval/exec
• use certain modules
• etc...

Current tests are unacceptable, as none of the tests provide meaningful feedback message, and they behave like test.expect.

Oh yeah, there are no random tests either. The tests are also very weak, so it is not very hard to just pass the tests without implementation a correct solution.

What is python?

author has had five years to open a window to let the haze out, proof read, and get to the point. surely this should get retired, this isn't what a published piece of text should read like.

Am I the only one not seeing any sort of specifications in the description? What am I even trying to do?

the hell is this

Python 3.8 should be enabled.

errrr... Why is there this comment in the initial solution?

# create an array called websites that has "codewars" as its only value

x)

Done

kata broken (python) by the new runner. Need corrections

to_string() is essentially a wrapper for impl Display. I think this is the u64 implementation of it: https://doc.rust-lang.org/src/core/fmt/num.rs.html#199-258 Looks like there is some cost, but I can't speak to how much of it is optimized out in release mode.

Does to_string cost much?

anyone.