Unresolved issues from the LLVM 15.x release

[h-vetinari]

@mgorny

but I’d like to note that this is a dangerous default when linking to shared LLVM libraries / dylibs

Given that the version number would change (by definition, up to bugs) when the ABI does, what dangers do you see for this?

Quoting some (IMO) relevant context from the previous thread:

@aaronpuchert

[…] libclang.so would not be the only library that doesn’t increase the SO version with every release. Just staying in the field of compilers, my GCC 12 comes with libasan.so.8, libatomic.so.1, libgcc_s.so.1, libgccjit.so.0, libgfortran.so.5, libstdc++.so.6, and a couple of others. On our side there is libc++.so.1.