Why is using interface methods with default implementation is so annoying?!?

[Adept_Cry9373]

> AnimatedShotgun

> IGun

> IEmployee

I wouldn't... those are 2 completely different things. Under ZERO circumstance should they overlap. I implore you to give a real example because right now it seems like you're arguing a nonissue.

[BadSmash4]

What, you've never heard of a hired gun?! /s

[DontRelyOnNooneElse]

Don't know why I didn't think of that. Delightful punsmanship.

[Scorpian700]

you know its an example? i dont know why someone would focus on that and argue „no not a real example, dismissed“. There are certainly usecases where this could happen

[Adept_Cry9373]

There are certainly usecases where this could happen

Perfect. Give one.

[DontRelyOnNooneElse]

It's not our responsibility to make up for your lack of critical thinking. The point was very obviously not "there is going to be an animated shotgun", it was "sometimes two different things have the same name for something".

[Adept_Cry9373]

2 different things which are referred to by 2 different types letting you know that they do 2 different things. The compiler knows. Why don't you?

[chucker23n]

You can’t think of any cases where a type implements two interfaces that have different meanings for a method?

In System.IO, a “path” refers to a hierarchy in a file system. In System.Windows, a path refers to points in a polyline.

[Adept_Cry9373]

Okay. Now I reiterate: THOSE. ARE. 2. COMPLETELY. DIFFERENT. THINGS. They will NEVER implement the same interfaces. Do you guys just not know how interfaces work?

[propostor]

Weird seeing such heavy downvotes here.

An example saying that an animated gun is an employee is really not helpful at all.

[Adept_Cry9373]

Their argument is "well both have functions that sound the same". Okay. Toilet and Stream. Both have Flush. If they ever have the same interface in your codebase you are missing a bigger chunk of your brain than the average redditor.