Expansion of global lambda expressions is broken

[neobrain]

Lambda expressions at global scope generate unintelligible output. C++ Insights is supposed to replace them with equivalent, explicit class definitions, but this only seems to work properly for lambda expressions defined inside a function.

The following table illustrates the output for a locally defined lambda (fine) vs. two instances of global lambdas (broken).

Input	C++ Insights
int main() { auto x = [a=5](int b) { return b*a; }; }	int main() { class __lambda_10_14 { public: inline /*constexpr */ int operator()(int b) const { return b * a; }     private:     int a;     public:     __lambda_10_14(int _a)         : a{_a}         {}   };  __lambda_10_14 x = __lambda_10_14{5}; }
auto x = []() { return 5; };	__lambda_1_10 x = /* public: inline ~() noexcept; */ static inline int __invoke(); ;
auto x2 = [a=5](int b) { return b*a; };	__lambda_5_11 x2 = /* public: inline ~() noexcept; */ [inta=5](int binline constexpr int operator()(int b) const { return b * a; } ;

[andreasfertig]

Hi Tony,

thanks for reporting that with Tony-Tables :-) Surprisingly I have no test for a global Lambda.

The AST matchers are still a source of trouble. Next step is matching the whole TU. But that will take some time.

However, patch is on its way.

[neobrain]

Happy to help, thanks for the quick fix :)