Add support for named fakes

[thomaslevesque]

I just found myself in a situation where I have a collection of fakes, and an assertion fails on one of the fakes, but I don't know which. It would be handy to be able to name fakes, e.g. something like this:

var foo1 = A.Fake<IFoo>(options => options.Named("foo1"));
var foo2 = A.Fake<IFoo>(options => options.Named("foo2"));

Then we could have an assertion failure message like this:

Assertion failed for the following call on <foo1>:
  Blah.IFoo.Bar()
Expected to find it once or more but no calls were made to the fake object.

The name could also be used for arguments in calls list. (e.g. Blah.IFoo.Bar(<baz>)).

For A.CollectionOfFake<T>, we might need to introduce an additional overload that takes the index into account:

var foos = A.CollectionOfFake<IFoo>(10, (options, index) => options.Named("foo" + index));

[blairconrad]

I'm super curious about this. For the collection, I can see it happening. I would like to know how it happened to you without using a collection.

[thomaslevesque]

I would like to know how it happened to you without using a collection.

I had a collection; I just didn't create it with A.CollectionOfFake<T>.

[blairconrad]

thomaslevesque added this to the vNext milestone an hour ago

Thanks. I'd accidentally added the PR and fixed that, but forgot to readd this!

[blairconrad]

This change has been released as part of FakeItEasy 5.1.0.