Hi, On Thu, Nov 24, 2016 at 9:33 AM, Haddock <ffm2...@web.de> wrote: > > Here is another blog that shows a way how to do this: > http://objectscape.blogspot.de/2013/09/inner-pattern-to-mimic-method.html >
Clever! I would like, though, to underscore the conclusion reached by the original post author: My preliminary conclusion of all this is to use the "inner pattern" in Go as an ex-post refactoring measure when code starts to lack "too much" in transparency. To apply it to begin with is too much pain where the gain in the end is uncertain. Otherwise, only apply it ex-ante when it is clear from the beginning that the flexibility will be needed anyway... With this I agree fully. /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.
