Patrick Steinhardt <ps@xxxxxx> writes:
> Yeah, in general I'm also of the opinion that we shouldn't bother. But
> in libgit2 we have pipelines that use such older compilers, and we don't
> want to drop those for now. So I think we should treat the reftable
> library specially, doubly so as this is the only instance that causes
> problems.
Hmph. Shouldn't there be some kind of "shim" layer where these
things are defined per project convention and/or toolchain being
used? So when building for git proper, you'd use {0} just as
everybody else do, but for others your include file supplied by that
project would use something else (like {{0}} in this case)? That
kind of approach would be a better solution than open coding QSORT()
in the longer term, for example.
