12 // passed to a kernel. Test that passing the given function to the unique
13 // stable name builtin and then to the kernel throws an error because the
28 // then an empty lambda is passed to kernel.
30 // then passing a different lambda to the kernel still throws an error because
31 // the calling context is part of naming the kernel. Even though the given
32 // function (F2) is not passed to the kernel, its mangling changes due to
33 // kernel call with the unrelated lambda.
55   // because the kernel uses do not interfere with each other or invalidate  in kernel3_4func()
79   // using the lambda in a way that does not  contribute to the kernel name  in main()
86       [=]() { l5(); }); // Used in the kernel, but not the kernel name itself  in main()
90   // using the same lambda in the naming of a kernel does not cause a diagnostic  in main()
91   // on the kernel use due to the change in results to the stable name.  in main()
95   kernel_single_task<class kernel6>(l6); // Used in the kernel name after builtin  in main()
98   // Same as kernel11 (below) except make the lambda part of naming the kernel.  in main()
100   // passing a second lambda to the kernel does not throw an error because the  in main()
102   // not change the mangling of the kernel.  in main()
111   // it to a kernel called with an if constexpr branch does not cause a  in main()
128   // passing a second lambda capturing the first one to the kernel does not  in main()
130   // kernel i.e., the mangling does not change.  in main()
139   // passing it to the kernel as a template template parameter does not cause a  in main()
140   // diagnostic on the kernel use due to template template parameter being  in main()
141   // involved in the mangling of the kernel name.  in main()
149   // and then calling the macro within the kernel does not cause an error on the  in main()
150   // kernel.  in main()
196 // kernel-ordering and lexical lambda ordering issue.