We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Found two things that stood out as odd.
Case A
auto foo() -> decltype([](){ return 4; });
This defines a lambda class but then uses it like this
__lambda_5_24 foo(); () -> decltype([](){ return 4; });
Which does not seem like correct C++
Case B
using x = decltype([](){ return 4; }); auto foo() -> x;
Which should be the same as Case A but the output does seem more correct but it does not define a lambda class.
using x = decltype([](){ return 4; }); __lambda_19_20 foo();
Insights link. https://cppinsights.io/s/51754024
The text was updated successfully, but these errors were encountered:
Hello @olafurw,
thanks for reporting this. A fix is on its way.
Andreas
Sorry, something went wrong.
6d9137a
Merge pull request #494 from andreasfertig/fixIssue490
e290a97
Fixed #490: `FunctionDecl` at TU scope with a trailing-return...
No branches or pull requests
Found two things that stood out as odd.
Case A
This defines a lambda class but then uses it like this
Which does not seem like correct C++
Case B
Which should be the same as Case A but the output does seem more correct but it does not define a lambda class.
Insights link.
https://cppinsights.io/s/51754024
The text was updated successfully, but these errors were encountered: