-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
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
False negative with statement ending with parens #42
Comments
One more example
This shouldn't be rewritten with:
|
Should or shouldn't? The second is consistent with the style. |
The first is also consistent with the style. |
It is not, the style prescribes no hugging braces (unless on a line with only braces) |
sadly... |
No not sadly, that's how this tool is designed. If you don't like that style, don't use the tool! 😆 This issue is about making more constructs get rewritten in that way |
This tool is very useful Because I really find this style useful:
I don't want to expand this line |
Tough! The tool can't possibly determine """semantic value""" I don't know what to tell you |
oops... This case works fine for me
add-trailing-comma doesn't touch it! Problem is only with this
|
Look, I think you're missing the point. The whole goal of the tool is so you don't argue about style. |
The tool just shouldn't touch this case
And also shouldn't touch this case too
They are both valid A person can choose according to "semantic value" or some other "magic" he likes |
I'm sorry, the first one is ugly and will continue to be rewritten. Please stop |
PyCharm Reformat Code works exactly that way i want
ok |
Very sorry for my inattention. |
I expect to be rewritten to
But I imagine the same code that prevents this from being rewritten is firing:
which I don't think should be rewritten.
Need to come up with a more clever heuristic here.
The text was updated successfully, but these errors were encountered: