Very interesting !!

why do you have so much time?

👍

Main reason is maintenance effort. There's 50 languages on CW, and each of them would have to have a package of anti-cheat measures which would have to be recognized, implemented, and maintained, only to be circumvented by some other clever tricks. It's considered infeasible. Authors are free (mostly) to implement whaever anti-cheats they want in their tests, but these can be still problematic, for example when a language version gets updated and an anticheat suddenly breaks things.

The banning method is much easier to implement, and works well.

Also, random tests are definitely required. Details below (so I can make a separate, spoiled post)

Well, turns out this kata has a lot of cheese possible: https://www.codewars.com/kata/reviews/621a6ba3ed65eb00011656cb/groups/64ded0a3798ed900010bddd8

Hello,

My advice to all Kata authors, add a proper validator

if (typeof(ClassName).Assembly == typeof(Assert).Assembly)
    for (;;);

Hi,

Small advise: don't use that again.

Cheers

Thank you!

I deliberately decided not to provide the "right answer" in the error messages (or the feedback) because:

1. It reveals the coefficients of the formula and makes it less challenging, IMO.
2. Formulas get monstrously huge really fast after certain input values; not only is it ugly, but also totally unreadable. I did not find it any more useful.
3. It is a secret, in the end :P.

On another note, I disabled exception raising.

Wow!

Nice Kata!!

But for now, the feedback is not very useful :

False should equal True

Moreover, an exception is raised when there is an error, this should be something like :

{User's answer} should equal {Right answer} for .

interesting format :)

Seriously . . ?