What version of Go are you using (go version)?
$ go version
go version go1.14 linux/amd64
Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
What did you do?
What did you expect to see?
a := [...]string{"no error", "Eio", "invalid argument"}
s := []string{"no error", "Eio", "invalid argument"}
m := map[int]string{1: "no error", 2: "Eio", -1: "invalid argument"}
What did you see instead?
is there some thing out of date
at https://golang.org/doc/effective_go.html#composite_literals

What version of Go are you using (
go version)?Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (
go env)?go envOutputWhat did you do?
What did you expect to see?
a := [...]string{"no error", "Eio", "invalid argument"}
s := []string{"no error", "Eio", "invalid argument"}
m := map[int]string{1: "no error", 2: "Eio", -1: "invalid argument"}
What did you see instead?
is there some thing out of date
at https://golang.org/doc/effective_go.html#composite_literals