Confusing overload resolution behavior with params object[] parameter when passing int[] vs string[] (or array vs collection expression)

[Youssef1313]

Two scenarios I found confusing:

Scenario 1

using System;

// Regular overload resolution works for both
var x = new MyAttribute(new int[] { 0, 1 }); // Okay
var y = new MyAttribute(new string[] { "Hello", "World" }); // Okay
var z = new MyAttribute([ "Hello", "World" ]); // Okay

[My(new int[] { 0, 1 })] // Okay
[My(new string[] { "Hello", "World" })] // Error
[My([ "Hello", "World" ])] // Okay - what?
public class C
{
    
}

[AttributeUsage(AttributeTargets.Class, AllowMultiple = true)]
public class MyAttribute : Attribute
{
    public MyAttribute(params object[] o)
    {
    }
}

Not sure if it's expected and why would "string" be very different from "int", and why collection expression is different. Both string and int are convertible to object. So to me feels like either both should error or both should be good. The former is a big breaking change.

Scenario 2

using System;

// Binds to object overload
var x = new MyAttribute(new int[] { 0, 1 });

// Binds to object[] overload. I don't see why they are different.
// This is just regular overload resolution, unrelated to attributes.
var y = new MyAttribute(new string[] { "Hello", "World" });

// Binds to object[] overload the same as array creation.
var z = new MyAttribute(["Hello", "World"]);

[My(new int[] { 0, 1 })] // Binds to object overload.
[My([0, 1])] // Binds to object[] overload
[My(new string[] { "Hello", "World" })] // Error. Should it bind to `object` overload?
[My([ "Hello", "World" ])] // Okay.. binds to object[] overload
public class C
{
    
}

[AttributeUsage(AttributeTargets.Class, AllowMultiple = true)]
public class MyAttribute : Attribute
{
    public MyAttribute(params object[] o)
    {
    }

    public MyAttribute(object o)
    {
    }
}