[Solved] What is the cause of this strange function declaration in GO?

Question

in go there are no classes in the way you usually see them .. instead we use the syntax in question do declare methods on types, the argument in front is called areceiver and if we use a pointer receiver we get reference type semantics otherwise you get value type semantics. check out the go tour it is awesome.

Accepted Answer

in go there are no classes in the way you usually see them .. instead we use the syntax in question do declare methods on types, the argument in front is called areceiver and if we use a pointer receiver we get reference type semantics otherwise you get value type semantics. check out the go tour it is awesome.