[go-nuts] Re: method resolution order

2020-09-16 Thread Stephan Lukits
Thank you for your effort! It's not so much about terminology but more about avoiding duplicate code. And a way to do that is abstraction and specialization (has not necessarly something to do with inheritance). So after your explanation I would then - factor everything from NotInS which can be

Re: [go-nuts] Re: method resolution order

2020-09-16 Thread 'Dan Kortschak' via golang-nuts
Yes, it's sort of like asking what the best way to translate "This sentence is not Spanish." into Spanish; you can do it, but it doesn't make a lot of sense. On Wed, 2020-09-16 at 02:13 -0700, Volker Dobler wrote: > On Wednesday, 16 September 2020 at 10:51:27 UTC+2 > stephan...@gmail.com wrote:

[go-nuts] Re: method resolution order

2020-09-16 Thread Volker Dobler
On Wednesday, 16 September 2020 at 10:51:27 UTC+2 stephan...@gmail.com wrote: > Assume a public interface I with two methods NotInS and M whereas NotInS > is calling M. An implementation i of I which implements NotInS and M as > well as a specialization s of i which only implements M. Finally