-> xparq/Out_of_Nothing/issues/625
- A possible use case is defining/configuring some ERROR macro locally inside a TU (-> but: immediate thought about the risks of header-spill e.g. for templated/inline crap!...)
In some TUs it should do the full Error(...) thing, in others it should only log.