Let's talk about why it is not recommended to use this/self for the receiver name in go.

This article brings you relevant knowledge about golang. It mainly introduces why it is not recommended to use this/self for the receiver name in go. What is the reason? If you are interested, let’s take a look. I hope everyone has to help.

Why is it not recommended to use this or self for receiver name in go?

In Go, receiver refers to the receiver as a method parameter, which can be a value type or a pointer type. When defining a receiver, it is not recommended to use this or self as the name of the receiver.

In other languages, such as Java and C, this or self are used to represent references to the current instance or object, but in Go, this and self are invalid identifiers and cannot be used for variable names or methods. name.

Although you can use this or self as a variable name or method name in Go, this does not conform to the style and convention of Go code. According to the Go code specification, it is recommended to use the first letter of the receiver type as the receiver name, such as:

type myType struct{}// value receiverfunc (m myType) myMethod() {
    // ...}// pointer receiverfunc (m *myType) myMethod2() {
    // ...}

Recommended learning: "go Video Tutorial"                                              

The above is the detailed content of Let's talk about why it is not recommended to use this/self for the receiver name in go.. For more information, please follow other related articles on the PHP Chinese website!