pkl97

Results 5 comments of pkl97

Did some more testing. The problem does **not** occur with clang 12.0.1 and 13.0.1 together with libc++, so it looks like a regression starting with clang 14. It is however...

Any idea when a fix for this issue could be available? I assume there is no chance for a backport to clang 15?

Interesting. I can confirm that the current 1.11.0 Doxygen trunk (51326cfc072bf6fe4ca13c60ca0e9faec1d38f82) does no longer show the warning (should have checked that before). But at least in my setup 1.9.8 also...

Thank you for the fix and the backport to clang 15.0.7! Works like a charm.

What is the state on the planned compiler warning that was mentioned before? We are also seeing this problem on a large multi-platform code base and it is a showstopper...