Have you considered the possibility of splitting the prepare-and-attack method into prepare and attack respectively? Even in a OO language, I generally try to avoid a base class being dependent on its subclasses. The subclasses may depend on the base class, but not the other way around. 2-ways dependency is usually a design smell.
-- 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.
