Mikkel Nylander Bundgaard

> After this change, inherently broken Is.SameAs usages would become compile-time errors because the generic overload will always be considered a better match even if the constraint doesn't match: I'm...

I'll close #742 as a duplicate of this

@CharliePoole I can take a look at it, but probably first tomorrow night or Sunday night as my days are packed (and I've not done much with cake the last...

@Rabadash8820 So far no one has started working on this

I guess the reason for why `NUnit1031` works is that it cares less about the concrete syntax, but rather uses the semantic representation - i.e. ```csharp internal static ImmutableArray AdjustArguments(this...

FYI - I've made a temporary workaround for the MacOS problem in #4950

I agree that this sounds like an error. The current comparison perform null checks and `ReferenceEquals` before determining whether it should use an externalComparer (aka custom comparer). Changing the existing...

@thomhurst I'm moving this to the `nunit3-vs-adapter` repo. Can you provide some more information about your setup - e.g. * are you running testes from the commandline or via an...

@manfred-brands As far as I can remember (this is more a guess than actual recollection) when I overtook the Analyzers project, then I ran the existing analyzers against all the...

Currently, NUnit2010 changes `Assert.That(nonNullInt is not null);` into `Assert.That(nonNullInt, Is.Not.EqualTo(null));` and then we can use NUnit4002 to change it into `Assert.That(nonNullInt, Is.Not.Null);` (and similarly for the other cases, but I...