Steven Weerdenburg

NUnit 4 added cancellation support at the test level though I don't believe this is yet tied into a higher level cancellation mechanism exposed to a runner to allow an...

I'm labeling this "bug" as this is something our changelog says we already did in #3810 and #4628

I like this idea. Improved observability and debugging experience is always a good thing

This hasn't received much activity in a while but seems in line with some other recent changes to start surfacing accidental misuse at compile-time. I'm promoting this from an `idea`...

Ok thanks that makes sense too @manfred-brands Mostly asked in case there was an unspoken preference within the team. I like the syntax sugar for adding and removing callbacks if...

Thanks @manfred-brands I had been thinking a discussion would be good too. I have been intending to get back to these, including your other PR. It's late here now but...

I like the idea of providing more strongly-typed constraints here with a more relevant subset of modifiers. I think we'd have to be conscious and mindful of breaking changes and...

@manfred-brands I feel like we've been approaching this differently and I find design discussions always harder in PRs. How would you feel if we moved the discussion to an issue....

From my own brief foray into this approach: ``` Assert.That(TActual actual, EqualNumericConstraint constraint) ``` I believe we'd need to take these changes right down to the resolver + builder to...

This looks good to me too, though one question I have is how we'd want code like this to behave: ```csharp [Test] public void MyTest() => Assert.That(1, Is.EqualTo(1).IgnoreCase); ``` A...