-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
Code Quality: Member can be static #15001
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
Comments
I don't like marking event methods and properties as static. |
I agree. We shouldn't make things static where it is not needed (The performance gain is negligent anyway). |
I think there are more important code quality issues, like #15000 and we can ignore this as the performance gain is negligent. |
I agree. In the meantime, closing. I would say we can add static accordingly when you work on another thing, not like this(not as the main purpose). |
Description
JetBrains Rider IDE suggests that methods with no instance usages and can be made static. But what’s the point? Well, as it turns out, static members yield a small performance benefit under particular circumstances.
Reference:
https://www.jetbrains.com/help/rider/MemberCanBeMadeStatic.Local.html
Concerned code
Gains
Requirements
Comments
Another case of "peanut butter", a change that individually aren’t hugely meaningful but that over time add up to bigger impact.
The text was updated successfully, but these errors were encountered: