Hey!
My peaks, that helped me a lot, back when I started with Go (depending on
what's your prefered way to learn and how fast do you have to learn it,
some might be less useful than the others. But it's worth to have the
options):
- Books
Go in Action — an extreamly good introduction to the
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
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:
On Wed, Sep 16, 2020 at 10:51 AM Stephan Lukits
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 a
> constructor whose
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
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 a
constructor whose return-type is I returns a pointer to an instance of
s.
