The thief cannot be a prince's friend. Thank you, I'll review the testcases and clarify it in the description

It should be async. Testcases are just updated, it should work now.

Kata description shows an asynchronous function but example test shows a synchronous function. Which is actually being tested? Handling synchronous/asynchronous functions involves completely different setups, so this needs to be clarified.

Didn't see that coming, edited now. Shouldn't be that easy🤔

My solution crashes the timeout test leading to an unexpected pass of the entire test suite (TBH I have no idea why :-P); you might want to look into it

Nice kata, thank you, but this drove me mad! I struggle to understand the other solutions, I think mine is optimal but overcomplicated.

Failed at random_small_test #9 is not a very useful feedback, a user can see this much even without the message. Failure message should be helpful for diagnosing potential issues, for example by presenting inputs of failed test cases. Printing to stdout is also discouraged if feedback can be presented in a reasonably good way with custom assertion messages.

Sure. Updated now.

Hi,

It's already in the description, but it's not obvious to find the info, when scanning the description: it would be cool to highlight what's the output type somewhere (maybe a ## Input/output section?)

Cheers