That means that before you check in your patch you should get policy
buy-in from the various maintainers and/or the SC. Otherwise, you'll
have provided technology that users will expect us to use in a
particular way, but that we may fail to use in that way.
I agree in principle, but as I have a limited amount of time allocated
to this, I would like to proceed with the implementation - and perhaps
leave the pragmas disconnected for now - to make the best use of my
time. Centralizing message processing, at least without the new
pragmas, does not itself add user-visible functionality but does allow
for more control over policies. I would like to be allowed to
implement the new code, assuming we agree on the issues that affect
its design, at least in parallel with policy discussions.
(My motivation here is to try to avoid what usually happens with this
issue - it get bogged down in policy and never actually gets
implemented. IMHO having an implementation that lets us implement a
policy, would get us *to* that policy faster.)