You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it can be seen from the generated code of the move assignment operator, the lambda is generated inside the if clause, and then called outside the if. The part from the generated lambda-class body and after the invocation of the lambda should be inside the if (surrounded by { and }).
The text was updated successfully, but these errors were encountered:
my pleasure! Thanks for reporting this. It took a bit longer than usual because this issue is not just present with if. It is wrong for while, do ... while, and for as well. As a bonus, the example above revealed that finalwas inserted at the wrong position. So you reported two bugs at once :-) A fix is on its way.
First of all, I want to thank you for making CppInsights, it is a great and handy tool.
Then, consider the following C++20 code:
As it can be seen from the generated code of the move assignment operator, the lambda is generated inside the if clause, and then called outside the if. The part from the generated lambda-class body and after the invocation of the lambda should be inside the if (surrounded by
{
and}
).The text was updated successfully, but these errors were encountered: