-
Notifications
You must be signed in to change notification settings - Fork 7
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
Increase the usage of compound assignment operators #29
Comments
Sorry, haven't seen this for a while. I'ld have thought that I am using compound operators pretty often, particularly at places where performance matters. If the diff created by your transformation script is so big that I can't review it in a reasonable amount of time then I won't accept it. |
Would you dare to take another look at the generated change suggestion? |
I'm a stupid Windows user, no Perl here. Give me a hint please ;-) |
How do you think about to try the shown search and replace pattern out by using tools you feel more familiar with? |
I can't because I do not understand what it is doing. Please explain me what it does. |
I propose to become more familiar with advanced applications of regular expressions here. The search pattern tries to find improvable assignments (in Java source code). The shown Perl command would adjust selected files in-place (after a file backup was performed). |
Thanks for the explanation. Actually I am roughly familiar with regular expressions but the command you posted is not that easy to understand. One day I might install a Linux subsystem and give it a go. |
The shown Perl command example is portable. |
👀 Some source code analysis tools can help to find opportunities for improving software components.
💭 I propose to increase the usage of compound operators accordingly.
Would you like to integrate anything from a transformation result which can be generated by a command like the following?
(:point_right: Please check also for questionable change suggestions because of an evolving search pattern.)
The text was updated successfully, but these errors were encountered: