Constructing, destructing and returning a value of arbitrary type T causes static assertion failure inside LLVM's frontend

[TymianekPL]

Program: x86-64 clang 19.1.0 (assertions)
Example: Compiler Explorer
Log (same output inside the CE link above): clang-log.txt
Given the code:

void nop(void) noexcept
{
    typedef int T;
    return T{}.~T();
}

LLVM frontend crashes with assertion failure:

clang++: /root/llvm-project/clang/lib/AST/ExprConstant.cpp:10704: bool EvaluateTemporary(const clang::Expr*, {anonymous}::LValue&, {anonymous}::EvalInfo&): Assertion `E->isPRValue() && E->getType()->isRecordType()' failed.

Removing return keyword and leaving T{}.~T(); compiles successfully.

[TymianekPL]

Seems to break on all versions after 10.0 (inclusive).
It compiles successfully on Clang 9.0.0, 8.0.0, ... up to Clang 2.7.0, and then it does not compile on Clang 2.6.0 with an error:

<source>:4:16: error: expected identifier
    return T().~T();

(note: changing brace initialisation to default constructor call produces the same issue on clang 10.*+)

[llvmbot]

@llvm/issue-subscribers-clang-codegen

Author: Tymianek (TymianekPL)

Program: x86-64 clang 19.1.0 (assertions) Example: [Compiler Explorer](https://godbolt.org/z/PWKsa6Tfc) Log (same output inside the CE link above): [clang-log.txt](https://github.com/user-attachments/files/17691513/clang-log.txt) Given the code: ```cpp void nop(void) noexcept { typedef int T; return T{}.~T(); } ``` LLVM frontend crashes with assertion failure: ``` clang++: /root/llvm-project/clang/lib/AST/ExprConstant.cpp:10704: bool EvaluateTemporary(const clang::Expr*, {anonymous}::LValue&, {anonymous}::EvalInfo&): Assertion `E->isPRValue() && E->getType()->isRecordType()' failed. ```

Removing return keyword and leaving T{}.~T(); compiles successfully.

[TymianekPL]

Seems like the code below compiles successfully.

void yes(void)
{
     using U = decltype([]{});
     using T = decltype([]{ return U(); });
     return T()().~U();
}

[TymianekPL]

So does

void yes(void)
{
     using U = decltype([]consteval{ using I = int; return I().~I(); });
     using T = decltype([]consteval{ return U(); });
     return T()().~U();
}

Which is a little weird, considering it uses the same code inside the lambda as the one that did indeed crash the compiler.. aha..