Welcome to C# 9.0

Post by oaiey » Thu, May 21, 2020, 5:49 AM UTC

The_rationalist wrote: post #29

tarasmatsyk wrote: post #26

I still think C# is one of, if not the best of designed languages exist. Even it moves in much smaller steps than it was before I think it's for good. I left .NET land at 6.0 and .NET 4.x versions mostly because of Windows eco-system (small open source community, almost no alternatives to out of the MS things, bad linux support). Since that I've been working with Java, Swift,JS, Python, Golang and I still think that…

To me C# is the second best designed language, the first being IMHO Kotlin. I'm very interested in what you think would make C# more well designed than the latter :}

Post by oaiey » Thu, May 21, 2020, 6:00 AM UTC

thelazydogsback wrote: post #158

tsomctl wrote: post #10

Well, we're getting closer to F#. Still waiting on discriminated unions and expression blocks. (Yes, I know, discriminated unions in F# are just implemented in the class hierarchy. But it's awfully nice syntactic sugar.) > Point p = new (3, 5); At first glance, not impressive, since you could just do: > var p = new Point(3,5); However, it would clean up code like: > graphics.DrawRectangle(RedBrush, new(3, 5, 2, 2))

I would love for C# to get rid of "new" as F# does -- why do we need it? var p = Point(3,5). For cases like this it's no big deal, but deep/complex initalizers (like expression trees, etc.) look horrible in C# unless you create static helper fn's to init objects.

Post by oaiey » Thu, May 21, 2020, 6:23 AM UTC

ThinkBeat wrote: post #150

I have worked with C# since the early beginning I have used it daily since then. I do know the ins and outs of the different up until C# 8 (latest released) and now .Net core. because I work with it every day. This probably an unpopular opinion but I wish they would make fewer changes to the language. A codebase from C# 2 will look entirely different than something written in C# 9. If you get a developer who has grea…

Post by oaiey » Thu, May 21, 2020, 6:27 AM UTC

Koshkin wrote: post #130

daeken wrote: post #27

Damn, this is fantastic. One big syntactical thing I should really put in a proposal for is null-conditional returns. Turning if(foo != null) return foo; Into return? foo; It fits perfectly with the existing null coalescing operators and such, while really cleaning up a lot of code.

An interesting idea; it could be extended to other constructs - assignments, method calls... Also, imagine having something like this: while (!return? foo) { foo = get_foo(); }

Post by oaiey » Thu, May 21, 2020, 6:33 AM UTC

jeffdavis wrote: post #115

_-david-_ wrote: post #91

Earlier quoted context omitted.

My understanding is that the dotnet runtime and powershell are both decent codebases. https://github.com/dotnet/runtime https://github.com/PowerShell/PowerShell

Looking at a random file in Powershell, the first thing I see is: private string _typeName; /// /// Add new type name to the specified object for TypeNameSet. /// [Parameter(Mandatory = true, ParameterSetName = "TypeNameSet")] [Parameter(ParameterSetName = "MemberSet")] [Parameter(ParameterSetName = NotePropertySingleMemberSet)] [Parameter(ParameterSetName = NotePropertyMultiMemberSet)] [ValidateNotNullOrEmpty] publi…