Alireza Habibi

@scalablecory >I would prefer to handle this in the params expansion rules than in overload restrictions. Have it explicitly expand into a Span if available, otherwise into an array/enumerable. As...

@svick wow didn't know that's a thing. I think that would permit using stackalloced Span storage also with references?

>Would the upcoming work on object stack allocation in CoreCLR (see dotnet/coreclr#20251) make this feature less important? I should note that due to required escape analysis on stackalloced memory, this...

> The params array usually does not escape the called function. @svick there's no restriction on the callee, it could freely leak out the array instance. That's not true of...

I think avoiding the redundant null check pattern will also resolve the issue with 'this', however we still do this when there's no other common receiver eg ```cs this.Prop1 &&...

@gafter You mean this doesn't cover constructors? I think there are a few other proposals about that and type inference in general (for instance: https://github.com/dotnet/csharplang/issues/92). I hope this can led...

> The property declarations and their accessor declarations must have the same modifiers One thing I like about partial classes is that you can add a part just by a...

@RikkiGibson > It also seems like source generators in practice just call UserDeclaration.Modifiers.ToString() inside their template and it tends to go pretty smoothly, though. For properties it's three places to...

While there's no restriction for types as mentioned (some other part could decide on static, for example), for member this could be simply not the case. Meaning, you either have...

duplicate of https://github.com/dotnet/csharplang/issues/583?