sstwcw wrote: > Another thing is that we need to get this fixed really soon. Another (safer > and actually preferred) alternative is to revert the change and address > problematic use cases before recommitting it, but I'm also fine with > forward-fixing this as long as fixes don't require major changes that have > potential for other problems to appear.
I see. In that case, I added #66372. However, why do you need it fixed so soon? The latest release is version 16. And the string breaking stuff isn't even in the version 17 branch. https://github.com/llvm/llvm-project/pull/66168 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
