Returing constant in interface implementation suggests impossible contracts

[microsoft]

Returing constant in interface implementation suggests impossible contracts

[RxDave]

Adding a post-condition shouldn't be a problem. Did you try adding it? If you're getting another warning or an error then it may be a bug in Code Contracts.

The rule is: You can't add preconditions to inherited members, but you can add post-conditions. See Liskov Substitution Principle.

[aarondandy]

While you can add post conditions I have found in my experience that CC seems to ignore them. Not sure if this is a bug or not.

[aarondandy]

When I make contract classes (sorry if my assumption is wrong) for interfaces I get around these issues by using abstract override or abstract to signal that I don't want to add a contract for that method or property.

In this case you could probably just do abstract bool ICollection.IsSynchronized { get; } and leave it out of your contract class.

[tom-englert]

You're right, adding a post condition works in this case. I expected to get the "x is implementing y, thus can't add contracts" warning - so I didn't try.