by joshlf13:

What does 'go version' print?
go version go1.2 linux/amd64

What steps reproduce the problem?
The easiest problem to demonstrate is the nil-pointer dereference, so I'll give that as
an example.

1. Pass an expanded slice as the varargs to io.MultiReader or io.MultiWriter
2. Set the first element of the slice to nil
3. call Read([]byte{}) or Write([]byte{})

Example on Go Playground: http://play.golang.org/p/Xy4YMB8g4J

What happened?
nil pointer dereference

What should have happened instead?
nothing (method should have returned normally)

Please provide any additional information below.
I have a patch ready if people decide that this is a worthwhile thing to patch. My patch
deep-copies the varargs slice. Original discussion included a suggestion of simply
documenting the behavior (golang-nuts thread:
https://groups.google.com/forum/#!topic/golang-nuts/oZgkDyxqmfQ).