Golang指针接收器技术混乱

Question

I recently started to learn Golang for a work project. I come from a 'c' background and have some confusion about the technicalities of Pointer Receivers in functions. Am I to assume receiver are generalized and don't care if the object is actually a pointer or a literal, it will translate it to whatever the receiver type is.

I know my question wording may be confusing so here is some code for example:

func (v *clients) makePtr() {
    (*v).slice = make([]client, 0)
    return
}

func (v clients) makeLit() []client {
    return make([]client, 0)
}

func main() {
    clsPtr := &clients{} // pointer
    clsLit := clients{}  // literal

    clsLit.makePtr() // literal with pointer reciever
    clsLit.makeLit() // literal with pointer reciever
    clsPtr.makePtr() // pointer with literal reciever
    clsPtr.makeLit() // pointer with pointer reciever
}

I expected the the functions with pointer receivers to only work on pointers and vice versa. from this am I just suppose to assume receivers are a blanket statement and don't care if its a pointer, literal?

EDIT: Apologizes guys, I may not have been to clear with my question, I understand that a pointer receiver is used to modify a object but I'm more confused as to the syntax, why does a pointer receiver work for both a literal and a pointer, since it receives a pointer shouldn't it only work on a pointer?

Answer 1

In golang these are called methods which are function with receiver. The receiver argument can be passed by value or by pointer.

You can write functions like below which are plain functions.

 type Client struct{}

//A pointer to Client    
func makePtr(c *Client){
    //do something with c
}

//A copy of client is made.
func makeLit(cs Client){
    //do something with c
}

Instead if you write methods then it gives association with struct.

type Client struct{}

func (c *Client) makePtr(){
    //do something with c
}

//A copy of client is made.
func (c Client)makeLit(){
    //do something with c
}

The main purpose of methods I see in golang is for interface implementation It is by virtue of methods structs implement (or satisfy) interfaces.