CC @griesemer for encoding/binary

Looks like binary.Read should return an error when passed data interface is not a pointer or slice.

intDataSize handles the case when dst arg is a simple/primitive value but binary.Read not.

Change https://golang.org/cl/184957 mentions this issue: encoding/binary: make Read return an error when data is not a pointer

It is not clear to me that the CL chose the right approach. Given that the Read function panics when other conditions that must be satisfied are not satisfied, it seems ok to panic in this case as well.

Marked as NeedsDecision.

My point is that in the case when a pointer to a struct is passed and struct itself is incorrect then the reflect-related code may (or may not?) panic.
It seems to me that documentation on Read is a little bit unclear.

I think we should do the same thing we do in the fallback case, which is

	if size < 0 {
		return errors.New("binary.Read: invalid type " + reflect.TypeOf(data).String())
	}

Shouldn't the behaviour be equal to other packages? Both encoding/json and encoding/xml is returning error.
https://play.golang.org/p/o9hl4rmIUDA

encoding/json and encoding/xml with int32 instead of struct{} : https://play.golang.org/p/KKE6ssLsBmy

Hello @griesemer, I am just prodding you about this issue. From the precedent, it seems to be that returning an error is alright. This issue is marked for Go1.14 and there is already a CL that's just waiting for your blessing https://go-review.googlesource.com/c/go/+/184957/, please take a look and thank you.

@odeke-em Thanks. On it.