Julien Couvreur
Julien Couvreur
@HaloFour The primary motivation for this proposal is readability/maintainability. Knowing that some code is isolated makes it easier to understand, review and re-use. That's the same general argument as with...
@HaloFour Any design involves some trade-offs and tensions. I recognize it is a fair concern to discuss and experiment with. From experience with static methods, I've found them to reduce...
Assigned to @cston for the remaining two work items (spreads and an additional check to iteration type)
Yes, any binding issues with collection expressions and extension members is part of this issue. This area ([scoped here](https://github.com/dotnet/csharplang/blob/main/proposals/extensions.md#collection-expressions)) should be considered uncharted at the moment
@CyrusNajmabadi I'm aiming to do this today
Closing as done
@cston @dotnet/roslyn-compiler for second review. Thanks
@cston @dotnet/roslyn-compiler for second review. Thanks
This falls out of current design. The error states: ``` // (6,10): error CS1061: 'int' does not contain a definition for 'Deconstruct' and no accessible extension method 'Deconstruct' accepting a...
@CyrusNajmabadi How did you get this stack trace? It seems really wacky, as it shows `SyntaxNode.get_Location()` calling `CSharpCompilation.CommonCreateErrorTypeSymbol(...)`, which I can't make sense of.