What does this actually achieve? As a downstream that adds register classes to multiple backends, whilst it's not difficult to adapt to, it's an annoyance to layer on top of all the other conflicts and refactorings that happen during each release cycle that has very little benefit I can see.
I realise, but there are countless violations of that throughout the tree, so I don't get why this one is so special that it needs changing now. Note that the coding standards *also* say:
There are some conventions that are not uniformly followed in the code base (e.g. the naming convention). This is because they are relatively new, and a lot of code was written before they were put in place. Our long term goal is for the entire codebase to follow the convention, but we explicitly do not want patches that do large-scale reformatting of existing code. On the other hand, it is reasonable to rename the methods of a class if you’re about to change it in some other way. Please commit such changes separately to make code review easier.