Go Methods on Values and Pointers
TLDR: I was surprised by the behavior of a method on a value. Should have used a method on a pointer instead.
This story starts when I was attempting to put together a simple web application using go. I was following the, what I believe to be good, recommendation of Alex Edwards on Organizing Database Access and was using dependency injection to provide some initialized resources to all my request handlers.
[Read More]