[all-commits] [llvm/llvm-project] 39549c: [clang] Fixed predefined expressions after lambda ...

StefanPaulet via All-commits all-commits at lists.llvm.org
Tue Jul 28 00:45:14 PDT 2026


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 39549cd7c62e9a2db44d186e0fe5d99e1473cb24
      https://github.com/llvm/llvm-project/commit/39549cd7c62e9a2db44d186e0fe5d99e1473cb24
  Author: StefanPaulet <tudor.stefan.paulet at gmail.com>
  Date:   2026-07-28 (Tue, 28 Jul 2026)

  Changed paths:
    M clang/docs/ReleaseNotes.md
    M clang/include/clang/Sema/ScopeInfo.h
    M clang/lib/Sema/SemaDecl.cpp
    M clang/lib/Sema/SemaExpr.cpp
    M clang/lib/Sema/SemaLambda.cpp
    M clang/lib/Sema/TreeTransform.h
    M clang/test/SemaCXX/source_location.cpp

  Log Message:
  -----------
  [clang] Fixed predefined expressions after lambda parameters (#211811)

After the parameter declaration of a lambda expression, `Sema` enters
the declaration context of the lambda call operator (in
`ActOnLambdaClosureParameters`), so the lambda specifiers and the
trailing return type are analyzed within that context. Because of this,
predefined expressions such as `__func__` resolve to the lambda call
operator, and not to the possibly enclosing function. (issue #122657)

Added a member to `LambdaScopeInfo` to mark whether or not the compound
statement of the lambda expression has been entered, to be used when
resolving a `PredefinedExpr`



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list