Joseph Musser

Previously discussed at https://github.com/dotnet/csharplang/discussions/738 (see HaloFour's comment too) Unfortunately the first time this was proposed (https://github.com/dotnet/roslyn/issues/13#issuecomment-173413281): > We have no expectation of ever doing anything like this. For the record,...

@bchavez Wouldn't it be better to treat records the same as ordinary classes, since that's what they output? How do you handle classes that have no parameterless constructor?

I was hoping this would make it over from /roslyn. Putting the namespace in the class name appeals to me the most since I have never, ever defined more than...

> The ambiguity about what the scope actually is comes about if multiple namespace x; directives are allowed in a single file. I don't see an ambiguity. Same with the...

For all my files that have a single namespace (which is all of them so far, personal and work, including every file I've ever edited or read in an open...

@bomzj First things first. :-) If the language supports it, Visual Studio templates will be able to be created eventually. (Speaking of which, for every console app I ever create,...

@ig-sinicyn I don't know if it deserves a down vote for those reasons. It's not a breaking change to any existing code. If you edit your code to start using...

@szalapski I don't think that's true, for the same reason that any operation that takes a `Foo` might not be able to take a `Foo`. This is what `in` and...

You use the nullability warning suppression operator, which is postfix `!`: ```cs DoSomething(list!); ``` It's called the https://docs.microsoft.com/en-us/dotnet/csharp/language-reference/operators/null-forgiving operator, but I'm calling it the null-blindness operator and hoping it catches...

Nevertheless, the operator is a nullability warning suppression operator and is the way intended for you to suppress this particular nullability warning.