catlover-bot wrote: Thanks for the feedback. The UNC round-trip example demonstrates a real flaw in this approach: collapsing doubled backslashes on each parse makes the transformation non-idempotent and can change a semantically meaningful UNC prefix.
More fundamentally, I agree that special-casing `\\` while leaving sequences such as `\t` uninterpreted is difficult to justify given that line directive filenames are now treated as header names and CWG2693 is still open. Rather than adding output-side re-escaping on top of this behavior, I think it is better to withdraw this approach. I am closing this PR. Thanks for catching this and for the explanation. https://github.com/llvm/llvm-project/pull/215992 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
