> one of my biggest pet peeves is when people take a Config object, which represents the configuration of an entire system, and pass it around mutably.
How do you create immutable structs in Go? I didn't think you could, which makes this more a Go problem than a `passing around Config object` problem.
(One of my pet peeves, coming to Go from C, is how little of stronger typing there actually is. In C, I pass and return const objects everywhere I can, my enums are not just ints because the compiler can warn when I forget one in a switch statement, etc).
How do you create immutable structs in Go? I didn't think you could, which makes this more a Go problem than a `passing around Config object` problem.
(One of my pet peeves, coming to Go from C, is how little of stronger typing there actually is. In C, I pass and return const objects everywhere I can, my enums are not just ints because the compiler can warn when I forget one in a switch statement, etc).