We're using code contracts for runtime argument checking. They are convenient and work beautifully.

Sent from my iPhone

On May 1, 2014, at 7:43 PM, "Denis Gladkikh" <notifications@github.com<mailto:notifications@github.com>> wrote:


In src/Splunk.Client/Splunk/Client/Contract.cs:

> @@ -0,0 +1,17 @@
> +﻿using System;
> +
> +namespace Splunk.Client
> +{
> +     #if __MonoCS__
> +     public static class Contract


I would recommend to remove CodeContracts at all from Source code. It is just a pain, which also takes more time for building.
CodeContracts can be really helpful when you really need to define contracts for interfaces, but for our case - we can just define our simple Contract class without injecting CodeContract code post factum.
I would say that it gives more pain for developers than benefits for maintainers.

—
Reply to this email directly or view it on GitHub<https://github.com/splunk/splunk-sdk-csharp-pcl/pull/7/files#r12218150>.