Joseph Musser

The problem will be if the synchronization context cannot be reused once the application exits. It doesn't seem acceptable to me to have a new synchronization context for each async...

Actually, I'm not sure. The starting point is that we're handling async way too low right now. What I can say a lot more definitively is that either WorkItem.Execute needs...

Here's one way to think about it: we need a system such that we call AsyncToSyncAdapter no more than a single time per test case, including all async setup methods,...

In an ideal world, `TestCommand.Execute` would be `ExecuteAsync` and return `Task`. This would allow you to implement this entire feature through your own `IWrapSetUpTearDown` attribute. But this would also be...

As far as I'm aware, there are no plans on the horizon for C# that would allow strongly-typed syntax like `Assert.That(myArray, Has.Property(s => s.Length));` where the compiler correlates the type...

@rprouse Can you give your thoughts on `actual.Should().Have.Property(s => s.Length)` as a potential addition to NUnit, versus Shouldly or FluentAssertions? We talked about this exact thing on Slack recently. For...

@CharliePoole I think we were on the same page. Thanks for clarifying. @rprouse I lean towards saying we shouldn't add new extension-method APIs that work just like Shouldly or FluentAssertions....

It looks like 'eligibility' must be defined in a way that doesn't depend on type inference, since type inference is part of overload resolution and 'eligibility' is being used to...

@HaloFour To me, shadowing is a feature. I occasionally shadow deliberately in order to prevent uncontrolled access to a field; `var controlledAccess = Interlocked.Exchange(ref this.controlledAccess, null);` for example. I've long...

Correct URL: