Representing State as interfaces in Go
I made up a neat little pattern in Go the other day. It’s a way to represent a state change in a system by exposing
different APIs for different states, while only holding state in a single underlying struct. I’m sure I’m not the first
person to invent this, and it may already a name, so please let me know if you know of one. I’m going to show an
instance of the pattern first and the motivation after.
The Pattern
// You start with a Resolver, and incrementally feed it data to be looked up
type ...
Read more at emoses.org