OverloadResolutionPriorityAttribute seemed no respected

[WeihanLi]

OverloadResolutionPriorityAttribute seemed no respected

[KennethHoff]

I haven't used it, but is this a case of "bigger number is lower priority"? E.g. use -1 instead?

[WeihanLi]

@KennethHoff from the comment here, a higher priority would be preferred

The priority of the attributed member. Higher numbers are prioritized, lower numbers are deprioritized. 0 is the default if no attribute is present.

https://github.com/dotnet/runtime/blob/7bc92926b36617f7a0646a8d936782bc4c3264ab/src/libraries/System.Private.CoreLib/src/System/Runtime/CompilerServices/OverloadResolutionPriorityAttribute.cs#L15

And when I add [OverloadResolutionPriority(2)] to the public static void OverloadTest2(params ReadOnlySpan<int> span) method, it produces the same output

[333fred]

While the attribute has indeed been merged, compiler support has not been implemented yet. That will happen, but until then, the attribute having no effect is indeed expected.

[WeihanLi]

@333fred should we close this when the support completed for the compiler

[333fred]

It is not useful to keep a bug open that tracks that we haven't yet implemented a feature. When we have a test plan issue, you can use that to track if we've implemented it.