@HananAbSh did you test this solution to find that out, or are you just assuming so?

Kata forked and updated to address all open issues

https://www.codewars.com/kumite/6899181990a07832ede399a2?sel=6899181990a07832ede399a2

Patch notes:

• Description amended to note that decorated functions must handle input args
• Tests extended to ensure positional and keyword args are handled appropriately
• Random tests added for timing
• Error messages added to test cases

Merged.

Sadly, Discord is blocked for me anyway, and I can't use it, but I think I'm just going to start creating kata with something easier like this, but more interesting.
Edit: But I can use Github instead.

If you ask your parents, with your use case, they might surprise you. ( and then you may have to surprise yourself, and not get lost in other servers than Codewars .. )

Discord would really help you. Tell your parents I sent you.

I think using Discord would help me a lot, but it's blocked in my school, and my parents probably won't let me use it. But I can still learn from other kata, and other people.

I wrote it myself.

Then having your first kata deal with randomness ( or floating points, in case you have any ideas in that direction ) maybe just isn't a good idea.

Without Discord, you'll have to go slow, because Draft kata won't attract attention and Beta kata will be held to quality standards. So you can't afford very many mistakes.

I've probably said it before, but I'll say it again: read Docs. all of 'em, slowly and carefully. read test suites of kata you've solved. solve more kata, read more test suites.

when a new Beta kata appears, follow its Discourse. lots of new authors make the same mistakes, and their kata tend to disappear into retirement soon, taking all issues with them. but if you have the link, you can still read a retired kata's Discourse.

If someone wants to help You can fork this

Yeah, I think I am going to Un-Publish this kata and change all these things (if I will be able to change them, I'm not that smart yet 😅)

I would, but I can't use Discord.

1. Don't post solution code in the discourse without a spoiler tag. It appears on the front page.
2. The code you posted doesn't work at all. Plus it looks nasty.

An author of the "fixed" version of the kata here. Would love to change the whole test cases section right this moment.

No offense to ZlataBrain but I, just as you all, have got so many questions about the way test cases were made. When I wrote a translation to the previous version of the kata, I knew the backlash was inevitable. Here it is and I can't even edit the task cause I don't have rights to do so.

In short, apologies to everyone, especially natan, complaining about the task. It was all because of my naive thoughts that I fully understand, how the task was designed.

including a character suggests at-least-one, which is what that tests

randomness isn't tested at all, nor is it a stated requirement. which. I mean. ... I don't even want to start that conversation xD

imo the kata should be considered a duplicate with no substantial addition (some flag handling) and leave it at that so we can avoid working out the rest

First fixed test has >10% chance to fail for (at least according to the current LLM slop description specifications) correct implementations. This is not how you test statistical randomness.

I also fear that your current reference solution would fail actual stats tests rather than the current ones which are specifically designed around it.