sergeyteplyakov/codecontracts.analyzer

Roslyn-based plug-in that simplify using Code Contract library

Code Contractor

Code Contracts like a charm!

codecontracts.analyzer's Issues

Investigate an ability to run this tool as a command line for VS2013

Not-null requires for indexers

Support for interface and abstract classes

Support for property setters

Not-null ensure for generic task-based method should should ensures on underlying result

I.e. for public Task<string> Foo() refactoring should generate Contract.Ensures(Contract.Result<string> != null), but not Contract.Ensures(Contract.Result<Task<string>>() != null.

More powerfull nullness analysis

Add Not-null requires/Add not-null ensures context actions should not be available on nullables.

For instance:

if method has return null, if (arg != null), var foo = arg?.boo etc.

Convert property postcondition to object invariant

Property postcondition and statement in ObjectInvariant method are equivalent.
The only difference that in some cases postconditions are hard to use, especially with C# 6.0 features like read-only auto-properties and properties with an expression body.

Refactoring that converts from one implementation to another would be very useful.

Example:

public DateTime TimeStamp? { get; } = DateTime.UtcNow;
public DateTime AnotherTimeStamp => DateTime.Utc.Now;

Preconditions for private methods

Preconditions are for public methods only! in private methods Contract.Assert/Contract.Assume methods should be used.

Benefits: performance benefits by disabling Assert/Assume but leaving Requires.

Fix can warn on this and provide a fix to convert to Contract.Assert/Contract.Assume.

Issue a warning for accessing fields in constructor precondition

Following code will lead to warning:

class Foo
{
  public readonly int N = 42;
  public Foo()
  {
    // error CC1011: This/Me cannot be used in Requires of a constructor
    Contract.Requires(N == 42);
  }
}

Extract CodeContracts.Analyzer.Core

Move the core logic out of the existing projects.
Reason: ability to use this logic in the different contexts.

Hint for missing precondition/postcondition for public methods

Tool can't warn (because of potential nullable types), but can emit an information tip to add Requires/Ensures for public methods (for public/internal types?).