Steven Weerdenburg
Steven Weerdenburg
If we are fine with the change in return typing merging into v4 but not the compiler error being introduced then an option could be to add the irrelevant properties...
I agree it could be considered a bug as we should be guiding users away from API misuse. I would argue that a case like this where we _know_ at...
From a release notes perspective, a type-safe constraint system could also be considered a "feature" even if it is just for equality checks on primitives at the moment
> Interesting thoughts! But if we create a new syntax, then we're in breaking water, right? So, can we do this with only fixing missing compiler errors ? On the...
> If it is the other way around, like the 3rd party is compiled with an older version, it is not an issue. The pre-existing code would have been compiled...
There's also a few filtering or selection bugs introduced in 4.x which may prove blockers for some to upgrade to NUnit 4. These aren't formally in the milestone at the...
Nothing from me, thanks @OsirisTerje
I think the ProgressWriter PR is pretty close to merging, just an issue with an unused using I think. Unsure if you wanted to wait on your end or not
I like this idea, I think it it's a nice usability improvement. The example has both the tuple + method arg names matching, but would we want parameter passing be...
The recent addition of generic `TestCaseData` classes may also help with strong typing here. To some extent, this could be considered a stylistic choice for those who wish to return...