Thanks for your comment! I would say this is a variation of the builder pattern that's more focused on doing this as part of the initialisation of the struct within the constructor.

​@@Tutorialedge Thanks for the info. I don't know GO and I randomly stumbled onto the video, but it all seemed so familiar to me. That being said, I have a lot of Java experience, and the builder pattern is very prevalent there. I have my own variation of the builder pattern. Basically, once you set up your standard getters and setters for a class, instead of having the setters return a void after they set the variable, they would return the class instance. example (might look weird in yt comments) public CustomClass setTitle(string title title){ this.title = title; return this; } What this allows you to do is chain commands when calling multiple setters. CustomClass custom = new CustomClass().setTitle("title").setValue("value").setRandomProp("random prop"); In "canonical" form this looks way uglier. CustomClass custom = new CustomClass(); custom.setTitle("title"); custom.setValue("value"): etc etc.. I don't know how "legal" this is, if there are any more implications under the hood, but I've never seen it being discussed anywhere as a possibility, and I find it more convenient than implementing the full builder pattern, while also abuses the autogeneration of classic setters, with just a minor modification, with the caveat that if you use build plugins (like Lombok for Java, that generates getters and setters on runtime), you'd still have to manually configure this setters. Sorry if it seems a bit random, but I hope it makes sense. I'd love to know if this is viable in GO and how it performs.

It is certainly something you could do in Go. I've thrown a code snippet together here - go.dev/play/p/oQhq3mAU7Nn The Effective Go documentation does have some guidance on the user of getters and setters here - go.dev/doc/effective_go#Getters

I finally figured out there was a ‘1’ at the end of it after all this time!