To make the API fluent, devs should be able to write matchers with builders

[craigfowler]

A little-used but important and under-developed feature is that of matchers and queries.

Currently there is no builder pattern for queries. This should be revisited to see if a builder pattern can be created, perhaps:

Query.For.Text()

Where, Query is a static builder class which has one static property. That property For creates a new query builder object. Anything else from that would be an extension method, which indicates the exact query object being used, and invokes a generic method on the builder, such that the value may be tested with a delegate.

[craigfowler]

In fact, combined with a builder for Matcher instances that could be shorter:

Matches.Query.ForText(x => x == "foo");

This way, the Query property of the static Matcher object would return a query builder, but the overall thing would return a matcher.

[craigfowler]

The combinator methods (And and Or) would then become extension methods upon a matcher instance.