When people attack your code, it isn't an attack on you. It makes your code better. It's one of the downsides to releasing any opinionated project (and many good projects are opinionated).
For my part, I won't use software written by someone who doesn't either refute criticism or use it to improve code, and I'm not satisfied you're doing either of those.
Thank you, you will be missed. I don't know what to do without you.
The comment that provoked you was rude and dismissive and the sort of thing we ask people not to post. That said, the guidelines here ask you to remain civil even when someone else is uncivil and/or wrong. That's an important rule that we all have to abide by—though it's a challenge, especially when one's own work is being discussed—because otherwise the discussion quality will rapidly deteriorate.
So please either make substantive neutral replies if you can, or don't post anything until you can.
But reading the comments in this thread this has gone overboard....to the point I, as a casual observer, had to say something.
I agree, "clearly written by someone who doesn't know the language well", _IS_ a direct attack on the developer and not the code. And I couldn't comprehend the mental gymnastics it would take to explain otherwise.
There is a major difference between:
"Why did you implement your own Queue here?" and "This guy doesn't understand C++. Don't use his code."
Don't let them win by giving into replying with a "Redditor" form of rebuttal filled with snark.
When reading your comments and code on the web, it seems like you're really an awesome dev, but you give in to hate comments by such people too easily.
I don't care how good your code/framework is if you blow up on just a minor bit of criticism. This is a great example where some comments in code could help teach people who don't know better.
Long gone are the days where the solo programmer could make important software without interacting with the rest of the outside world. Knowing when to check your ego at the door is just as important as getting the technical bits right.
Also, your work looks good. I want to use it.