No, I don't believe it does. I merged these changes into clang after that bug's closure date, and the issue is still present in what is currently shipped.
No, I don't believe it does. I merged these changes into clang after that bug's closure date, and the issue is still present in what is currently shipped.