Use OverloadResolutionPriority with Debug/Trace.Assert(string)

[stephentoub]

using System.Diagnostics;

SomeMethod(6, 10);

static void SomeMethod(int a, int b)
{
    Debug.Assert(a > 0);
    Debug.Assert(b > 0);
    Debug.Assert((a - 3) > (b / 2));
}

Before:

Process terminated. Assertion failed.
   at Program.<<Main>$>g__SomeMethod|0_0(Int32 a, Int32 b)

After:

Process terminated. Assertion failed.
(a - 3) > (b / 2)
   at Program.<<Main>$>g__SomeMethod|0_0(Int32 a, Int32 b)

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[dotnet-policy-service]

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

[KennethHoff]

inb4 this is also unexpectedly breaking akin to ICollection : IReadOnlyCollection 😅

[stephentoub]

inb4 this is also unexpectedly breaking akin to ICollection : IReadOnlyCollection 😅

How is this breaking?

[KennethHoff]

No idea. It was a bad joke. It's similar-ish DX improvements to old APIs so it would be (not..) funny if they both had similar reasons to not be improved; back compatibility breaks.