3 ms·
Do you have examples of unreadable C#? The language didn’t change much IMHO. You have new features, like records, but C# code looks pretty much like what I star
by dgellow 2y ago
Do you have examples of unreadable C#? The language didn’t change much IMHO. You have new features, like records, but C# code looks pretty much like what I started with in 2009
- leetharris 2y agoNow that I'm thinking about it, most of it is probably .NET bloat instead of C# bloat, but a few examples would be global usings, file scoped namespaces, records, target-typed new expressions, null coalesce assignments, etc. It's nothing huge, but combined with .NET bloat it can be overwhelming when you haven't worked in .NET for a while.
- jenscow 2y agoand pattern matches, primary constructors, range operator, switch expressions, etc. it does add up
- eknkc 2y agoI came to love pattern matching so much that now when I write TypeScript I get frustrated. It is a weird balance.
- dgellow 2y agoAll of this looks and feels like C#. That doesn’t look unreadable or a completely different language. In fact they end up making C# more readable by removing boilerplate
- wvenable 2y agoAll the things you describe make C# more readable and easier to understand! Are you really confused by file scoped namespaces or target-typed new or even null coalesce assignments? You don't have to use them -- although Visual Studio will helpfully suggest places you can use them. If I had never seen a pattern match switch statement before (and there was a point where I didn't) it's sort of immediately obvious what it does.
- francisofascii 2y agoThis one threw me off when I first saw it: (int x, string y) = (default, default);