ReSharper 2016.3 Help

Code Inspection: Member can be made static (shared) (private accessibility)

Consider the method Print below:

public void Foo() { Print("John"); } private void Print(string name) { Console.WriteLine("Hello, {0}!", name); }
Public Sub Foo() Print("John") End Sub Private Sub Print(name As String) Console.WriteLine("Hello, {0}!", name) End Sub

ReSharper suggests that Print has no instance dependencies 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.

Here’s what the MSDN documentation has to say about it:

- Members that do not access instance data or call instance methods can be marked as static (Shared in Visual Basic). After you mark the methods as static, the compiler will emit non-virtual call sites to these members. Emitting nonvirtual call sites will prevent a check at runtime for each call that makes sure that the current object pointer is non-null. This can achieve a measurable performance gain for performance-sensitive code. In some cases, the failure to access the current object instance represents a correctness issue.

Last modified: 12 October 2017

See Also