On 6/8/21 12:57 PM, Bruno Haible wrote: > The difference between lib/ and tests/ is that code in lib/ goes into > the binaries delivered by the packages, and therefore if a package > maintainer makes an effort to silence a warning, we will consider > their patch. Whereas for tests, as I said, it is too much > of an effort/cost to do so.
One little aspect of the tests code is that people might look (also) there to learn how to use a certain gnulib module, and then copy/paste the code from there into their projects. That's at least true for the good test cases, surely not for those provoking errors. This means it may be worthwhile to have at least the good test cases in a warning- free shape (which I think it most often already is). Have a nice day, Berny
