Proposal : Avoid empty methods about scanf

[anuviswan]

Expression-bodied Metod with Expression.Empty()

Sample Non-Complaint Code

public void Foo() => Expression.Empty();

Expresion.Empty() intends to be used in scenarios where an expression is expected, but no action is desired. This would point towards an intentional behavior rather than a code smell. At this point, this scenario would be considered a complaint code unless further questions/discussions rise in the topic.

[anuviswan]

Option to remove Empty Methods

In addition to option to add exception in empty methods, there should be additional code fix that enables to remove the method all together. This raises two scenarios.

• Unused Empty Methods

Non-complaint Code

public class Bar
{
 public  void Foo
 {
      var item = 3;
      // Do something else     
 }

 private void FooInternal()  // Unused and Empty
 {
 }
}

FooInternal in the above scenario could be removed. The method is unused and is empty. This should not provide an problem while removing.

• Used Empty Methods
  This is a slightly more complex scenario as the references needs to be evaluated.

Non-complaint Code

public class Bar
{
 public void Foo()
 {
 }
}

public class BarExtended:Bar
{
 public void MethodInChild()
 {
   Foo();
 } 
}

The method could be invoked from another assembly as well. The usage path/tree needs to be tracked before removing the method.

Could be better if this option is deferred till another release

[anuviswan]

Documentation remaining