alanphipps added a comment.
We've also been seeing failures in our downstream Arm compiler when running the
Perennial C++14 compliance tests related to this change. Specifically, the
tests expect a diagnostic to be issued when the lambda capture variable is
outside of the lambda's {} scope. Another tests uses the lambda capture
variable in a decltype-style return type which is also outside of the scope.
Do these failures sound like what others have run into?
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D119136/new/
https://reviews.llvm.org/D119136
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
