Blair Conrad

Sorry for confusion. I mentioned the scopes for history, and to jump in front of anyone else doing so. I agree. They were fraught. Yeah, I thought about the same...

Rejecting #1840 due to points that @thomaslevesque brought up in side chat. The PR was inadequate, missing several use cases and behaviours that we'd like to have. To summarize, `ResetToInitialConfiguration`...

> > We may need to extend the rule definitions with a Clone option or similar. Which would be a breaking change, unless handled carefully. I'll look into that as...

I've been slow on this, partly due to external commitments, and partly because I'm a little bit torn over the feature. I appreciate the value, but am slightly uneasy about...

@afelinczak, thanks for chiming in. I'd considered storing multiple snapshots on the Fake as well, but had imagined a stack of snapshots in that case. I never put fakes in...

> In DI scenario we would likely to need only one snapshot. Thanks. To be honest, I'm not sure when anyone would ever need more than one… > If snapshots...

Intriguing, @thomaslevesque. > ref/out parameters could be supported, but would require a custom delegate that matches the method signature Does this mean someone would have to declare ```c# delegate int...

Thanks for your interest, @LukeMarlin. Can you given an example of how these would be used, contrasted with the current usage? That way we can more easily see the benefit.

It's an intriguing idea. I was going to say I'd never felt a need, but probably in the past I've done something like configured a call to store its arguments...

Keying off `IReturnValueArgumentValidationConfiguration` (and similar interfaces/classes, as there's more than just `IReturnValueArgumentValidationConfiguration`) could be useful, but another useful overload may be something like ```c# var calls = Fake.GetCalls(() => fake.Send(A.Ignored));...