"and i have to check it for length....which i apparently dont know how to do" (21:35) haha awesome. Great video!
@calvinwilson3617
3 жыл бұрын
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
@andrewgeorge7459
2 жыл бұрын
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...
@MajeureX
2 жыл бұрын
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.
@bajicdusko
3 жыл бұрын
21:33 😂, had a good laugh there.
@aspdotnet
Жыл бұрын
Thanks Chris, this is awesome
@SenthilKumaran4u
3 жыл бұрын
Excellent video, thanks.
@JetBrainsTV
3 жыл бұрын
You are welcome!
@ME-dg5np
2 жыл бұрын
Tks! 👍
@voswouter87
3 жыл бұрын
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.
@alphaprimal1669
3 жыл бұрын
I think it's a safe way to emulate multiple inheritance, and with the coming addition (I think it's gonna make it to C# 10) of static interface members, we can use interfaces as a primitive way to emulate traits. it's usefull for lib writers ig.
@parvejsolkar123
2 жыл бұрын
🔥
@mikhaildervel1561
2 жыл бұрын
discards for exceptions look strange and unclear. My opinion
@MiningForPies
3 жыл бұрын
Default implementation of interfaces is an abomination. It is not a good feature, it defeats the entire point of interfaces.
@shrikantbmali
3 жыл бұрын
It doesn’t introduce any new problem that wasn’t already there…
@MiningForPies
3 жыл бұрын
@@shrikantbmali it does introduce a problem, it puts implementation in an interface, which goes against the paradigm of interfaces not containing implementation details that has existed for decades. It’s hard enough stopping people writing brittle code with shitty abstract classes without then spreading its disease into interfaces.
@buddysteve5543
Жыл бұрын
Many of these new "features" of C# are crap! They seem to make a project more unreadable and to really know what is going on, you have to be up to date with all the little newly builtin syntaxes and symbols and such! It's not elegant at all!! :(
@benjamininkorea7016
2 жыл бұрын
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).
Пікірлер: 19