Here is a short article about how to do OOP in Go with composition, structurally typed interfaces and, in some special cases, embedding. I believe this can often be a better approach than traditional OOP modeling using inheritance. I'd love to hear you thoughts.
Inheritance and OOP: Go one better <http://yourbasic.org/golang/inheritance-object-oriented/> -- 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.
