[clang] [clang][NFC] Don't track OpaqueValueExpr in bad conversion sequence (PR #238243)
Younan Zhang via cfe-commits
cfe-commits at lists.llvm.org
Tue Nov 3 01:20:04 PST 2026
================
@@ -6210,12 +6208,9 @@ static ImplicitConversionSequence TryObjectArgumentInitialization(
ExplicitParameterType = Method->getFunctionObjectParameterReferenceType();
OpaqueValueExpr TmpExpr(Loc, FromType.getNonReferenceType(),
ValueKindFromClassification(FromClassification));
- ImplicitConversionSequence ICS = TryCopyInitialization(
- S, &TmpExpr, ExplicitParameterType, SuppressUserConversion,
- /*InOverloadResolution=*/true, false);
- if (ICS.isBad())
----------------
zyn0217 wrote:
I don't think other paths matter here, the only thing we're focusing on is on-stack OpaqueValueExpr and what we need to do is to avoid them escaping from ICS. And the bad conversion sequence is the only one that leaks them - we store types for successful conversion sequences.
https://github.com/llvm/llvm-project/pull/238243
More information about the cfe-commits
mailing list