Comments on: Contract Annotations in ReSharper 7

By: Dmitri Nesteruk

Dmitri Nesteruk — Sun, 31 Mar 2013 10:52:08 +0000

@Michael @foo setting forceFullStates=true causes R#’s analysis to become pessimistic, i.e., if the state of a variable is unknown, R# will assume that the variable might be null.

By: foo

foo — Thu, 28 Mar 2013 12:15:05 +0000

I’ll repeat Michael’s question and ask, what’s the forceFullStates parameter for?

By: Allon Guralnek

Allon Guralnek — Mon, 22 Oct 2012 16:08:29 +0000

What about “null => exception” Or is this the same as “null => halt”?

By: Jura Gorohovsky

Jura Gorohovsky — Wed, 12 Sep 2012 19:54:23 +0000

@Jason
This comment explains why.

By: Jason Newell

Jason Newell — Wed, 12 Sep 2012 15:26:10 +0000

Really disappointed that Resharper has decided to invent their own form of code contracts rather than support the Microsoft version.

By: Sergey Kuks

Sergey Kuks — Fri, 31 Aug 2012 11:16:19 +0000

@repka, If both null and not-null input may produce null output you probably better use CanBeNull annotation instead, because there is no obvious correlation between input and output.

By: repka

repka — Fri, 31 Aug 2012 10:35:59 +0000

Awesome feature, one thing irked me though: what do you mean by null => null being “automatically complemented with notnull => notnull”? Is this a mistake? Why can’t notnull => null in some cases? How about true => false. Is it “automatically complemented” with false => true? I can understand such thing to be introduced for compatibility with some obsolete format of annotations, but if so, you should get rid of it as soon as possible, if you plan to keep these contracts for a while and extend them, stuff like that will cause trouble.

Talking about extending them: please take a look at my proposal for Cleanup Annotations feature here: http://youtrack.jetbrains.com/issue/RSRP-329639 . It covers not only IDisposable tracking, but tracking of any values which must be somehow released, closed, completed, exited or cleaned up in any other way. E.g. files, sockets, transactions, identity impersonations, monitor locks, reader/writer locks, etc.

By: Jura Gorohovsky

Jura Gorohovsky — Mon, 20 Aug 2012 21:12:37 +0000

@Martin, Lars-Erik
Unfortunately support for Microsoft Code Contracts per se is not on the schedule for the reasons stated in this comment

By: Lars-Erik Aabech

Lars-Erik Aabech — Mon, 20 Aug 2012 10:48:21 +0000

Ref @Martin. (+1)
Microsoft Code Contract support would be awesome.

By: Sergey Kuks

Sergey Kuks — Fri, 17 Aug 2012 08:48:59 +0000

Here are some answers:
halt, vois and nothing all means the same (and left for backward compatibility) and used to mark method that break control flow by throwing exception or terminating program. I.e. the
[ContractAnnotattion("null => halt")]
void AssertIsNotNull(object x) {
if (x == null)
throw new ArgumentNullException(”x”)
}

We did not manage to provide intellisense for the expressions yet, the only thing we did is error highlightings.