efriedma-quic wrote: > That seems reasonable, however, there are other QOI reasons for attempting to > generate globally unique names for lambdas
Sure. But we wouldn't want to special-case vftables for that. > I think our strategy to ensure internal lambdas like this are globally unique > is that they appear in some externally visible scope which can only be > defined once, and that scope gets mangled into the name of the lambda. Is > that happening here? I don't have an MS demangler handy to confirm against > the test case. In the testcase, the lambda is just at global scope. Not sure what you're expecting to happen here. https://github.com/llvm/llvm-project/pull/71748 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
