@techee ACK :) Anyway I reproduced it with clang 14 on my Linux machine as well, so it's not specific. And I read the warning existed at least since 5.0 so… anyway, #4230 should fix it.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.