Makes sense 👍

I think since there's little chance we'd actually remove the original array version in the foreseeable future, and considering there might be scenarios in which it generates a warning (e.g. old compiler versions?), perhaps we drop the obsolete attribute?

Gave a bit of thought to whether we'd also want to provide a params ReadOnlySpan version, too; seems like it'd cover a slightly different set of cases and still be an option in a later version if we decided to include it then, so probably not, but just mentioning it in case you spot any conflicts/synergies with that hypothetical API.

perhaps we drop the obsolete attribute

done

Gave a bit of thought to whether we'd also want to provide a params ReadOnlySpan version

added

i also added some tests

i also removed the OverloadResolutionPriority. since if we want to keep the array varient around, there is no need to redirect

nudge

turns out i still need the OverloadResolutionPriority to point the compiler to the most efficient overload