hopefully "fixed" now with 5e997f4dba1cfcde554ff413a615e101b9c72ee5 I just disabled that chunk of code on earlier clang releases, means people might miss some warnings, but that's a fairly unlikely warning for normal coding to hit