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
Split out from #586:
Original code:
body = combineStatements( new ExpressionStatement( lvalue.buildAssignment( new VariableGet(variable), voidContext: true)), body);
Becomes:
body = combineStatements( new ExpressionStatement(lvalue .buildAssignment(new VariableGet(variable), voidContext: true)), body);
I'm not sure why the heuristics pick the latter, but it would be nice if it could pick the former without making other code look worse.
The text was updated successfully, but these errors were encountered:
The forthcoming tall style gives you:
body = combineStatements( new ExpressionStatement( lvalue.buildAssignment(new VariableGet(variable), voidContext: true), ), body, );
That looks pretty good to me. It does a better job of showing the nesting structure of the calls.
Sorry, something went wrong.
No branches or pull requests
Split out from #586:
Original code:
Becomes:
I'm not sure why the heuristics pick the latter, but it would be nice if it could pick the former without making other code look worse.
The text was updated successfully, but these errors were encountered: