我有一个关于empty struct
s 的基本问题,并且我试图在尝试获取两个切片的支持数组元素的地址时得到以下不同输出:
a := make([]struct{}, 10)
b := make([]struct{}, 20)
fmt.Println("&a == &b", &a == &b)
fmt.Println("&a[0] == &b[0]", &a[0] == &b[0])
Run Code Online (Sandbox Code Playgroud)
上面的代码片段返回:
&a == &b false
&a[0] == &b[0] true
Run Code Online (Sandbox Code Playgroud)
但是,考虑到以下稍微改变的片段:
a := make([]struct{}, 10)
b := make([]struct{}, 20)
fmt.Println(a[0], &a[0])
fmt.Println("&a == &b", &a == &b)
fmt.Println("&a[0] == &b[0]", &a[0] == &b[0])
Run Code Online (Sandbox Code Playgroud)
上面的代码片段返回:
{} &{}
&a == &b false
&a[0] == &b[0] false
Run Code Online (Sandbox Code Playgroud)
有人可以解释上述差异的原因吗?谢谢!
[跟进]进行以下修改:
package main
import "fmt"
type S struct{}
func (s *S) addr() { fmt.Printf("%p\n", s) }
func main() {
a := make([]S, 10)
b := make([]S, 20)
fmt.Println(a[0], &a[0])
fmt.Println("&a == &b", &a == &b)
fmt.Println("&a[0] == &b[0]", &a[0] == &b[0])
//a[0].addr()
//b[0].addr()
}
Run Code Online (Sandbox Code Playgroud)
仍然返回相同的输出:
{} &{}
&a == &b false
&a[0] == &b[0] false
Run Code Online (Sandbox Code Playgroud)
但是,取消注释方法调用,返回:
{} &{}
&a == &b false
&a[0] == &b[0] true
0x19583c // ==> [depends upon env]
0x19583c // ==> [depends upon env]
Run Code Online (Sandbox Code Playgroud)
在进一步深入之前,请知道根据规范,程序无论为大小为零的值生成相同还是不同的地址都是正确的,因为规范仅声明它们可能相同,但不要求它们必须相同相同。
如果结构体或数组类型不包含大小大于零的字段(或元素),则其大小为零。两个不同的零大小变量在内存中可能具有相同的地址。
所以你体验到的是一个实现细节。做出的决定还有更多细节和因素,以下解释仅对您的具体示例有效且充分:
在第一个示例中,切片的支持数组的地址仅在函数内部使用main()
,它们不会转义到堆。您打印的只是地址比较的结果。这些只是bool
值,不包括地址值。a
因此编译器选择对和的后备数组使用相同的地址b
。
在第二个示例中,后备数组的地址(更具体地说是后备数组的某些元素的地址)在函数外部使用,它们main()
被传递到函数内部并在fmt.Println()
函数内部使用,因为您也在打印这些地址。
我们可以通过将-gcflags '-m'
参数传递给 Go 工具,要求它打印逃逸分析的结果来“证明”这一点。
在第一个示例中,将代码保存在 中play.go
,运行go run -gcflags '-m' play.go
命令,输出为:
./play.go:10:14: "&a == &b" escapes to heap
./play.go:10:29: &a == &b escapes to heap
./play.go:11:14: "&a[0] == &b[0]" escapes to heap
./play.go:11:38: &a[0] == &b[0] escapes to heap
./play.go:8:11: main make([]struct {}, 10) does not escape
./play.go:9:11: main make([]struct {}, 20) does not escape
./play.go:10:26: main &a does not escape
./play.go:10:32: main &b does not escape
./play.go:10:13: main ... argument does not escape
./play.go:11:32: main &a[0] does not escape
./play.go:11:41: main &b[0] does not escape
./play.go:11:13: main ... argument does not escape
&a == &b false
&a[0] == &b[0] true
Run Code Online (Sandbox Code Playgroud)
正如我们所看到的,地址不会逃逸。
运行go run -gcflags '-m' play.go
第二个示例,输出为:
./play.go:10:15: a[0] escapes to heap
./play.go:10:20: &a[0] escapes to heap
./play.go:10:20: &a[0] escapes to heap
./play.go:8:11: make([]struct {}, 10) escapes to heap
./play.go:11:14: "&a == &b" escapes to heap
./play.go:11:29: &a == &b escapes to heap
./play.go:12:14: "&a[0] == &b[0]" escapes to heap
./play.go:12:38: &a[0] == &b[0] escapes to heap
./play.go:9:11: main make([]struct {}, 20) does not escape
./play.go:10:13: main ... argument does not escape
./play.go:11:26: main &a does not escape
./play.go:11:32: main &b does not escape
./play.go:11:13: main ... argument does not escape
./play.go:12:32: main &a[0] does not escape
./play.go:12:41: main &b[0] does not escape
./play.go:12:13: main ... argument does not escape
{} &{}
&a == &b false
&a[0] == &b[0] false
Run Code Online (Sandbox Code Playgroud)
正如您所看到的,a[0]
转义&a[0]
到堆,因此 的后备数组a
是动态分配的,因此它将具有与 的b
地址不同的地址。
让我们进一步“证明”这一点。让我们修改第二个示例,以获得第三个变量,c
其地址也不会被打印,让我们b
比较c
:
a := make([]struct{}, 10)
b := make([]struct{}, 20)
c := make([]struct{}, 30)
fmt.Println(a[0], &a[0])
fmt.Println("&a == &b", &a == &b)
fmt.Println("&a[0] == &b[0]", &a[0] == &b[0])
fmt.Println("&b == &c", &b == &c)
fmt.Println("&b[0] == &c[0]", &b[0] == &c[0])
Run Code Online (Sandbox Code Playgroud)
运行go run -gcflags '-m' play.go
此程序,输出为:
./play.go:11:15: a[0] escapes to heap
./play.go:11:20: &a[0] escapes to heap
./play.go:11:20: &a[0] escapes to heap
./play.go:8:11: make([]struct {}, 10) escapes to heap
./play.go:12:14: "&a == &b" escapes to heap
./play.go:12:29: &a == &b escapes to heap
./play.go:13:14: "&a[0] == &b[0]" escapes to heap
./play.go:13:38: &a[0] == &b[0] escapes to heap
./play.go:14:14: "&b == &c" escapes to heap
./play.go:14:29: &b == &c escapes to heap
./play.go:15:14: "&b[0] == &c[0]" escapes to heap
./play.go:15:38: &b[0] == &c[0] escapes to heap
./play.go:9:11: main make([]struct {}, 20) does not escape
./play.go:10:11: main make([]struct {}, 30) does not escape
./play.go:11:13: main ... argument does not escape
./play.go:12:26: main &a does not escape
./play.go:12:32: main &b does not escape
./play.go:12:13: main ... argument does not escape
./play.go:13:32: main &a[0] does not escape
./play.go:13:41: main &b[0] does not escape
./play.go:13:13: main ... argument does not escape
./play.go:14:26: main &b does not escape
./play.go:14:32: main &c does not escape
./play.go:14:13: main ... argument does not escape
./play.go:15:32: main &b[0] does not escape
./play.go:15:41: main &c[0] does not escape
./play.go:15:13: main ... argument does not escape
{} &{}
&a == &b false
&a[0] == &b[0] false
&b == &c false
&b[0] == &c[0] true
Run Code Online (Sandbox Code Playgroud)
由于 only&a[0]
被打印,但不&b[0]
被打印&c[0]
,因此&a[0] == &b[0]
will befalse
但&b[0] == &c[0]
will be true
。