[llvm-branch-commits] [clang] release/18x: [clang] Avoid -Wshadow warning when init-capture named same as class … (PR #84912)

sheredom wrote: Yeah indeed - its not a clang 17 regression. It's a _clang 16_ regression. At the minute we're holding our internal compiler toolchain on clang 16, and for our users we've got to special case disable the warning entirely for clang 17.

[llvm-branch-commits] [clang] [clang] Avoid -Wshadow warning when init-capture named same as class … (PR #84912)

https://github.com/sheredom edited https://github.com/llvm/llvm-project/pull/84912 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits

[llvm-branch-commits] [clang] [clang] Avoid -Wshadow warning when init-capture named same as class … (PR #84912)

https://github.com/sheredom created https://github.com/llvm/llvm-project/pull/84912 …field (#74512) Shadowing warning doesn't make much sense since field is not available in lambda's body without capturing this. Fixes https://github.com/llvm/llvm-project/issues/71976 >From

[llvm-branch-commits] [clang] [clang] Avoid -Wshadow warning when init-capture named same as class … (PR #84912)

https://github.com/sheredom milestoned https://github.com/llvm/llvm-project/pull/84912 ___ llvm-branch-commits mailing list llvm-branch-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits