On 2024-02-19 03:03, Bruno Haible wrote:
writing #include <...> everywhere has
very little benefit.
There is a benefit: it's simpler and would avoid future problems like
the one just fixed.
Currently we have more-complicated guideline, which is that one should
use #include <...> for include files in category A, and that you can use
either style for files in category B, and that these categories are
explained somewhere in the documentation. (Also, a file may migrate from
category B to category A in the future; this isn't explained yet....)
It'd be simpler to say "It's better to use #include <...>."
Whatever guideline we use, either the contributors need to learn the
guideline, or we can politely adjust their code once contributed. I
don't see why a simpler guideline would discourage contributors; quite
the contrary.
