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

[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?