How come "which isn't that easily to provide in compiler explorer, " suddenly becomes me telling that was impossible?
If you enjoy typing a endless list of clang-tidy flags on a tiny text box, well fun is on the user.
The first concern is that some parts of the industry keep reaching to C when there are better alternatives, even the language authors have moved on to creating better languages.
I've looked at them -- not all of them but all that I've looked at were the same kind recommending memcpy_s instead of memcpy, and were ridiculously easily to classify as false positives. So yes.
> How come "which isn't that easily to provide in compiler explorer, " suddenly becomes me telling that was impossible?
You claimed it wasn't easy but it is easy. VERY easy. It's one flag to disprove your point. Be honest.
> The first concern is that some parts of the industry keep reaching to C when there are better alternatives, even the language authors have moved on to creating better languages.
Many still enjoy it, are productive, and are creating infrastructure for billions of people to use. Let's keep things in relation.