This forum is for those wishing to discuss moderation and reporting issues regarding content on the site.
Specifically, discussions on:
Whether a given article is suitable for publishing
Discussions on whether a question should be edited or improved, or simply marked as "not a question" or "Incomplete"
Discussions on members who are causing problems but not to a point where you want to report them as abusive. Maybe you want to discuss how to approach them about the manner in which they ask questions, or their behaviour regarding their articles. Our goal should be to coach members in how to treat the community fairly while ensuring the site is free of debris.
Tips for new moderators
Discussions on overall editorial policy and direction
CodeProject has always erred on the side of being accepting and coaching rather than elitist and insulting, and my intention is to keep it like this.
However, it's important to always encourage appropriate behaviour and stop inappropriate behaviour. This forum is the place to discuss where that line is drawn.
With regards to the article mentioned above, I feel that in addition to C++, it would be good to have C# sample as well as C# is more relevant. Would like to know what others feel about this article...
I feel that the article would fit better as a Tip.
I don't see what language choice has to do with the moderation of an article, though. If an author chooses to write their article/tip in C++ then it's exactly that, a C++ article/tip. It should not be held back just because it's not your language of choice or because another language is more "relevant".
A Quick search shows that the author has also posted the same article in DZone.com which is ok, But when I get to the bottom of the article he has links that point to a commerical website. which also is hosting a webinar with the same title.
Deleting items from somewhere in the middle of an std::vector takes O(n) time. This is because the resulting gap from removing an item must be filled by moving all the items which come after the gap one slot to the back.
While moving items around like this, which might be expensive if they are complex and/or very large and include many items, we preserve their order. If preserving the order is not important, we can optimize this, as this section shows.
That is followed by naming the author and the source:
Jacek Galowicz, author of C++17 STL Cookbook propose his quick_remove_at function for removing elements from std::vector by moving the last element to removed position.
But the citing is not indicated and from reading it is not clear that it is a citation.