It's partly by the type system. You can implement a std::sort (or slice::sort()) that just delegates to qsort or a qsort-like implementation and have roughly the same compile time performance as just using qsort straight.
But not having to is a win, as the monomorphised sorts are just much faster at runtime than having to do an indirect call for each comparison.
Issues shouldn't really live in the same source tree, IMO. But AFAIK there are forges that keep the issues in the same repository, just not in the same tree of commits that the source tree has, git notes style.
Isn't the issue that some people work around MOT decibel limits? After all they only need to pass the decibel limit on the MOT test, and not on the road in regular use.
The engineering solution approach doesn't seem to be fundamentally different to speed cameras.
I don't see any LibreOffice related processes on my Debian machine, but I have it installed. Does it do that on Windows only, or distros disable this by default?
But not having to is a win, as the monomorphised sorts are just much faster at runtime than having to do an indirect call for each comparison.