Replies: 2 comments 1 reply
|
Would that only apply to the very first occurence (before any find operations)? |
1 reply
|
I would not prefer to have this, I would probably disable such rule. If you often have to read the code the reset is convenient knowing you don't have to inspect the procedure if anything else is happening to the variable prior to the code line you are looking at. It is valuable to have this insight. In my opinion readability outweighs reduction of code lines. The reset (most likely) doesn't have any performance overhead. Also be aware the KISS principle might cause false positives in repeat loops. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Started from this post.
On local scoped variable, it's redundant to do a
Clear(Customer)and/orCustomer.Reset().All reactions