|
From: Mike C. <mik...@gm...> - 2007-08-16 13:04:34
|
The code itself (around line 256 of Internal/ExpectationBuilder.cs) is straightward; it's an easy fix, and would actually make things tidier because we wouldn't need overloads. The fact that this ~300-line class has no unit tests whatsoever is a little embarrassing... M. On 16/08/07, Steve Mitcham <Ste...@ty...> wrote: > There was some discussion a while ago on this issue. I'm not sure that > it ever got entered as a bug. I've been bit by it when dealing with > 'out' parameters (example: With(1,2,Is.Out) fails) > > I think that adding the matcher to the list using the coalescing > operator would be pretty readable > The following example is without having a chance to look at the code in > question, so I hope you get the gist > > expectations.Add(x as Matcher ?? Is.EqualTo(x)) |