I recommend re-writing them using real-world examples, where they really 
are the "best solution", rather than a facilitated example.

Often beginners learn from such facilitated examples and end-up misusing 
and getting the wrong idea about them. Using realistic examples helps to 
avoid those problems (to some degree).

On Friday, 2 February 2018 19:03:54 UTC+2, matthe...@gmail.com wrote:
> I’m looking at patterns summarized on Wikipedia from “Design Patterns: 
> Elements of Reusable Object-Oriented Software” and writing out a few as the 
> equivalent in Go.
> Visitor: https://play.golang.org/p/A5tNzxMmetH
> Abstract Factory: https://play.golang.org/p/SWwuX49eysd
> Factory Method: https://play.golang.org/p/FRgDBx2CLFf
> Facade: https://play.golang.org/p/forPdwy9VCi
> Proxy: https://play.golang.org/p/DFWuDPTOzEP
> I’m curious how more experienced people rank these and the other patterns.
> Matt

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.

Reply via email to