diff options
author | Younan Zhang <zyn7109@gmail.com> | 2024-03-16 12:56:11 +0800 |
---|---|---|
committer | GitHub <noreply@github.com> | 2024-03-16 12:56:11 +0800 |
commit | 3e69e5a15782a5776a3245170aeb5d97ef746fa5 (patch) | |
tree | 00519b36c99ab1c07ff6ec6fa3803f0cb33e70a1 /llvm/lib/CodeGen/ModuloSchedule.cpp | |
parent | 5a3cc7ba24c564a19a7812efd79ecd224b8193f5 (diff) | |
download | llvm-3e69e5a15782a5776a3245170aeb5d97ef746fa5.zip llvm-3e69e5a15782a5776a3245170aeb5d97ef746fa5.tar.gz llvm-3e69e5a15782a5776a3245170aeb5d97ef746fa5.tar.bz2 |
[Concepts] Add Decls from the outer scope of the current lambda for conversion function constraints (#83420)
This fixes the case shown by
https://github.com/llvm/llvm-project/issues/64808#issuecomment-1929131611.
Similar to
https://github.com/llvm/llvm-project/commit/f9caa12328b265b77221fe7a310d4504673d814a,
we have some calls to constraint checking for a lambda's conversion
function while determining the conversion sequence.
This patch addresses the problem where the requires-expression within
such a lambda references to a Decl outside of the lambda by adding these
Decls to the current instantiation scope.
I'm abusing the flag `ForOverloadResolution` of
CheckFunctionConstraints, which is actually meant to consider the Decls
from parent DeclContexts.
---------
Co-authored-by: cor3ntin <corentinjabot@gmail.com>
Diffstat (limited to 'llvm/lib/CodeGen/ModuloSchedule.cpp')
0 files changed, 0 insertions, 0 deletions