As I said before, Go's flavor of OO is different from that of other languages. Don't try to map concepts one-to-one, or you will end up with very contrived solutions. Always look at the big picture (why am I doing this?) and don't get side-tracked by synthetic examples.
Most important is defining the correct interfaces (how your objects should behave, what services they should provide); implementation reuse is secondary. You will always find more than one ways to avoid repeating the same code, on a per-case basis and you can always improve on that down the way, provided that your interfaces are correct. Just my 2c /npat -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
