That's fine. But we probably prefer for chalk to compile libcon4m with pinned recent compiler versions, so it'd be nice for the libcon4m repo CI to use the same versions. Especially since recent compiler releases are in the habit of erroring by default for constructs that used to tolerated, see for example:
With https://github.com/crashappsec/libcon4m/commit/14604adf6ca68c75a08360129d71beb63571c1d1, we build libcon4m in CI with:
That's fine. But we probably prefer for chalk to compile libcon4m with pinned recent compiler versions, so it'd be nice for the libcon4m repo CI to use the same versions. Especially since recent compiler releases are in the habit of erroring by default for constructs that used to tolerated, see for example:
and it's better for CI to fail in a PR in the libcon4m repo, than to fail in a chalk PR that bumps libcon4m.
I'll create this ticket to track using the most recent release of clang somewhere, when that makes sense. We could do that by either:
The first is probably easier and slightly more useful.
It's also nice to use pinned recent compiler versions if at some point we enforce that, for example:
See also the list of LLVM releases.