There are a lot of cool and usable new features being added to C#. However, way too many of us are too busy building stuff, and …
13 Comments
Leave a Reply
You must be logged in to post a comment.
There are a lot of cool and usable new features being added to C#. However, way too many of us are too busy building stuff, and …
You must be logged in to post a comment.
Compressing code into single lines creates a concise complexity that looks very impressive to non-geeks. Super cryptic.
But for real geeks, creating and disposing of a zillion temporary variables not only makes the code harder to read & digest, it also makes the code much more difficult to debug if something goes wrong.
Readability and maintainability are important.
You never now who is going to inherit your code…
🔥
Amazing list, and extremely thorough and well-explained. I knew maybe 70% of them at most, so instant Suscribe. I have one that I remember discovering last year:
if (myInterfaceObject is ImplementationA ImpA) { ImpA.DoStuffSpecificToImplementationA(); }
I use this in Blazor for multiple test questions, that might have images, or audio, or various special features like drag and drop, but use the same scoring interface (elo adjustments and so on).
Tks! 👍
"and i have to check it for length….which i apparently dont know how to do" (21:35) haha awesome. Great video!
discards for exceptions look strange and unclear. My opinion
There's no mention of local functions! That's my favourite feature since it allows you to compose complex methods into smaller units without polluting the class level scope.
What's the advantage of default implementations over abstract classes?
Seems to me there's a big disadvantage: interfaces can now have implementations…
That increases complexity and readability of the code.
21:33 😂, had a good laugh there.
Default implementation of interfaces is an abomination. It is not a good feature, it defeats the entire point of interfaces.
Excellent video, thanks.
Awesome! I will no longer hate tuples!!
Great video! One additional good use i have found for default interface methods is when you will have multiple implementations of the interface, but know they should have identical implementations for some of the functions. This will be great for blazor code where you should keep implementations for both server and client seperate, but also with minimal code