Fred Silberberg
Fred Silberberg
@RikkiGibson I don't think 17.9 is right. I don't expect that we can address this in C# 12.
> Isn't the natural type related to the collection type? e.g. List vs string[] etc.? How would that solve this problem? Yes, it is, and that's exactly why it would...
> But what happens if you decide that the natural type is List and the overloads receive string[] and IFormattable[]? Would the taget-typed algorithm kick in again in that case,...
> it should not be too time-consuming to just adapt it to collection expressions before the C# 12 release This is never a safe assumption to make :laughing:
> But hopefully you give it a try. It isn't going to happen. The cutoff date for such changes is basically today. It will be a post-release thing.
> Agree this is the most likely outcome but the spec should be clear about this. No previous specification I'm aware of has been clear about this, I'm not sure...
@AlekseyTs I've addressed your feedback on this. For VB, let's iron out what we want to do for C#, and then look at adapting it to VB.
> IIRC c.M([42]) would be resolved to Span, right? No. Quoting from the proposal: > Because this pruning occurs at the very end of the overload resolution process, it does...
> I think they should affect Extension methods as well. This way I can upgrade those too. They do, but as worded currently, only within the same type. For example:...
I'm going to go ahead and merge this so we can put the open questions on the LDM agenda.