I have been writing Go programs for a little bit now and have found them not too bad to write. It is a C-style language that makes picking it up easy if you come from nodejs or C#. But, there are some weird nuances that you have to get use to if you do decide to pick up some Golang.
Here goes the list:
I think golang is going back to the header and source file roots on this one. Basically, you define members and function signatures in your type signature. Then if you want to define the implimentation, you would make sure you add the type before the function name, like this example:
package data import ( "io/ioutil" ) type IDataAccess interface { Save(key string, value string) Load(key string) string } type File\_access struct { FileLocation string } func (r File\_access) Save(key string, value string) { ioutil.WriteFile(r.FileLocation, []byte(value), 0777) } func (r File\_access) Load(key string) string { var value, \_ = ioutil.ReadFile(r.FileLocation) return string(value) } This shows that the interface IDataAccess describes the method signatures, and File\_Access describes the fields of the struct. But in order to implement a File\_access struct, you need to add a (r File\_access) to tell golang that you are part of that struct. Weird.
While many of these items are complaints, I do enjoy the language. I just wish some of these language paradigms were cleaned up thats all. If you can explain some of these to me, leave a comment!