• There should be more random tests (~ 100). Random tests shold always cover both valid and invalid (no path) cases.
• Returning different types (list/bool) is bad practice. When there isn't a path the function shopuld return a "no-value" (None in python) or raise an exception.

The assertion messages should provide information about what was wrong (see the docs).

As dfhwze noted, this isn't likely to be approved, but it's good to know for another kata.

fixed there

Lots better, thanks.

I changed the Show instance in preloaded, let me know if that works better.

In Haskell, the Crates add frustration only.

Please can the Show instance make them transparent? The current instance maximises visual clutter, with the useless color accessor.

Approved. This looks great! Thanks for your work on this.

Haskell translation

The description has been updated only to distinguish language-specific information.

Nice Kata (´▽`ʃ♡ƪ)

Had me stuck for a good bit! Very fun!

God no. You only need to test two or three of them really. Most of the tests in this case should be random.

Should I still keep the 1200+ modules or delete the whole thing?

oh ok i see, thank you so much, I'll tell you when I finish doing that, thanks for helping me with creating my first ever kata :)

No, I'm saying you need to generate your own modules at runtime if you want to stop me from hardcoding. Like generate modules which literally do not exist outside of your kata.

Remember, modules can be imported locally from the same directory as the running script.