Thanks for the response. I agree that your threshold is not unreasonable, but it would be nice if it was stated in the problem. It does feel kinda of bad to have to run the code a few times until you pass based on how your Random Generator calls go. Or perhaps you could edit the error message from the test to says "There are > 10% duplicates" or something. Ideally, I'd love for you to add the 10% threshold in the challenge text and the error message.

Letters should only go from A to F. This goes both to upper and lower case.
It seems you are calling every possibe letter in the alphabet.

To be clear: I did appreciate several of your katas and upvoted them. True, you're not getting paid for your work here, like everyone else. And, also true, nothing compels you to solve issues of an approved kata. There are many unsolved issues in many katas, that's the normal process of maintenance of a collaborative web like this one. Just please don't mark issues as solved when they are not.
Anyhow, thanks to Farekkusu for solving the issues in C++ version.

BTW I never approved any fork reverting changes

Fixed.

Are you joking? You've approved a fork which reverted the fix.

Edit: fixed it myself.

The method should be made static in the initial solution in C++.

it was then already resolved it, reissue when you have new details

It is not explained anywhere what the input parameter is for in C++.

Not getting paid does not prevent you from respecting the katas requirements. This is and remains a kata issue. I don't understand why you pretend I don't appreciate your effort. Raising an issue is not a personal offense against you, it's a note that aims to point out and help correct the kata's defaults. Many katas have.

actually @akar-0 I don't have to, and nobody can force me change the description without my consent specially because I'm not getting paid for this. This is a community and for that I allow on all my Katas to be edited by anyone. If you don't have something explicitly written or you can get to understand how some code works or don't want to spend time on that it's not a Kata issue, it's not a deffective problem. So don't pretend the excercise has an issue or is less useful because of a description added years ago for a non native english speaker like me when you are part of this community and you don't appreciate my effort or tried to help or rewrite the description.

I get the description, just it is incomplete for c++. See for example here : The description should clearly state all requirements the user is expected to fulfill to complete the kata. Unless the kata is a puzzle, users should not be given test cases that enforce requirements not mentioned in the description. The description should explicitly, unambiguously state which inputs have to be handled, which inputs do not have to be considered, and how to handle exceptional situations.