While it’s an interesting exercise to bring more OOP style to Go, I’m not sure it’s necessary. It’s fairly standard within Go to just do
myVar := &SomeStruct{}
Or
myVar := make(SomeStruct{})
Alternatively if you want to initialize a struct with default values, simply creating a New() function would satisfy this.
func NewStruct() *MyStruct {
return &MyStruct{Key: val}
}
Distraction-free reading. No ads.
Organize your knowledge with lists and highlights.
Tell your story. Find your audience.
Read member-only stories
Support writers you read most
Earn money for your writing
Listen to audio narrations
Read offline with the Medium app
Entrepreneur, software developer, writer, musician, amateur luthier, husband, dad. All opinions are my own.
While it’s an interesting exercise to bring more OOP style to Go, I’m not sure it’s necessary. It’s fairly standard within Go to just do
Hi Peter, thanks for your comment. I think perhaps I wasn’t clear in my post above – I strongly believe the only ‘style’ is the one that is consistent amongst the team, and strongly discourage arguing about anything style-wise as it’s effectively a…
--
A New function is the kind of initializer that was mentioned earlier in the post. the problem with it is that you need to go to great lengths to ensure/enforce your structs being created ONLY via the initializer (i.e. only initialized in a valid…
--
