Search results for query: *

The plan was something along the lines of this, where the named classes are just specific instantiations of the generic class providing a different exception type. Ultimately, the purpose of separating Expects from Ensures is: When reading code that uses them, it's clear what the author's...

Mmk, that's what I was afraid of. I was hoping to come up with a way to avoid duplicating the method signatures, but (unlike with C++) I guess that's not really a possibility here. Thanks though!

I'm trying to write something similar to the existing Debug class that allows clients to explicitly verify pre- and post-conditions of their methods. For example, to check a precondition that the input variable to a method is not equal to 0, one would use Expects.IsGreaterThan(input, 0), and...