cmd/compile: Pointer escapes when stored in a non-escaping map #63343
Comments
|
This is unfortunately working as intended. |
|
Now that you mention it, the comparison I made with slices was incorrect. Here, the pointer escapes from both the slice and map: package main
func escape_slice() {
i := new(int) //Escapes
s := []*int{}
s = append(s, i)
}
func escapes_map() {
i := new(int) //Escapes
m := map[int]*int{}
m[0] = i
}
func main() {
}I'll close this now since this bug report was motivated by a supposed gap in functionality between slices and maps. Thanks for the feedback! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of Go are you using (
go version)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env)?go envOutputWhat did you do?
Compiled this program with
go build -gcflags="-m"What did you expect to see?
./main.go:4:10: new(int) does not escape ./main.go:8:10: new(int) does not escape ./main.go:14:10: new(int) does not escape ./main.go:15:13: []*int{...} does not escape +./main.go:19:10: new(int) does not escape ./main.go:20:19: map[int]*int{...} does not escapeWhat did you see instead?
./main.go:4:10: new(int) does not escape ./main.go:8:10: new(int) does not escape ./main.go:14:10: new(int) does not escape ./main.go:15:13: []*int{...} does not escape -./main.go:19:10: new(int) escapes to heap ./main.go:20:19: map[int]*int{...} does not escapeThe text was updated successfully, but these errors were encountered: