Comments on Dennis Doomen.NET: The curious case of the unsolved extension methods...

I forgot about the "(string s) => s" ...

2010-03-26T13:52:54.308+01:00

I forgot about the "(string s) => s" syntax. That may be a reasonable workaround. Thanks Steven.

Don't be stubborn :-) Conditions does all the...

2010-03-26T13:19:51.560+01:00

Don't be stubborn :-)

Conditions does all these kind of tricks and is heavily based on extension methods. You can write your HaveCount method as follows:

public static ShouldConstraints HaveCount(this ShouldConstraints constraints, int expectedCount) where TCollection : IEnumerable
{
}

With your contain, you indeed hit the limit, but you'll just have to help the compiler a bit. This will work:

someList.Should().Contain((string s) => s.Length > 0);

I should rename 'Contain' to 'HasAny' or something like that. Contains is more something you'd use for having a certain element, like this:

public static ShouldConstraints Contains(
this ShouldConstraints constraints,
TElement element) where TCollection : IEnumerable
{
}

Good luck.

Hi Steven. I don't think so. The limits I'...

2010-03-26T12:20:22.460+01:00

Hi Steven. I don't think so. The limits I'm talking about are related to the resolution mechanism of extension methods. I know I can solve all of this if I let loose of the someObject.Should() syntax, but I don't want to...

The things you want to do are possible. I do these...

2010-03-26T10:15:08.585+01:00

The things you want to do are possible. I do these kinds of things with my CuttingEdge.Conditions library. Take a look at it (http://conditions.codeplex.com). I think you find a solution for your problems there.

For instance, users of this library can write the following lines without any problem:

void Method(System.Collections.ObjectModel.Collection ids)
{
Condition.Requires(ids)
.IsNotEmpty()
.HasLength(5)
.DoesNotContain(666)
.ContainsAny(new[]
{ 1, 2, 3, 4 });
}