orthoxerox

@Joe4evr Why would you want target-typed `new` for locals? There's `var` already. I would rather use it in function arguments.

@HaloFour I don't see why it can't be a ZCA for *struct* types. They get specialized copies of the generic methods, so baking the right implementation into each copy should...

@Bartmax `partial` is for classes in the same assembly. It simply combines several pieces of the same type during compilation. Extensions are for extending arbitrary classes, including those from external...

@333fred your example is missing a semicolon after the switch expression. @HaloFour There's #1597 for labeled loops and and even older https://github.com/dotnet/roslyn/issues/5883 with a WONTFIX resolution.

I agree with @gulshan, a more restricted feature for aliasing should come first. I imagine it could even avoid creating new types at all, something like this: ```c# public newtype...

~~@svick that's what will happen if you upgrade to the compiler version supporting nullable reference types, too.~~

@svick you got me confused there for a moment and I gave a hasty incorrect reply. There won't be a compiler error in most cases, "original type to newtype" and...

I agree. If we're going to get non-nullable reference types and structs with parameterless constructors, then we should be able to override `default` for them,

Please let me know if I'm hitting this limitation or a different one: When running nginx using docker, the correct way to use the [resolver](http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver) command is to pass it...

@m-reza-rahman Yes, that would work very well for destinations, I think. Annotation-based connection factory definitions (`JMSConnectionFactoryDefinition`) would also work, but many existing JCA resource adapters for MOM suffer from poor...