This is not reproducible to me.

go version go1.8 darwin/amd64
go version go1.8.3 darwin/amd64

I can't recreate it either. And the error frankly makes no sense. The reported error is:

../../../github.com/pebbe/zmq4/reactor.go:57: cannot use events (type State) as type int in field value
../../../github.com/pebbe/zmq4/reactor.go:57: cannot use handler (type func(State) error) as type func(int) error in field value

Line 57 of reactor.go is:

	r.sockets[soc] = &reactor_socket{e: events, f: handler}

The type reactor_socket is defined earlier in that same file as:

type reactor_socket struct {
	e State
	f func(State) error
}

So the error message is saying that in reactor_socket fields that clearly use the type State are instead using the type int. That makes no sense. The file reactor.go doesn't even use cgo.

@pebbe The zmq4 issue suggests that you are relaying a bug report from someone else. Can you recreate this problem yourself?

On the e-mail thread I asked for the diff of the work directories. Thanks for providing that. I looked through it earlier, and again just now, but I see nothing that could cause this kind of error. As noted the error is not in types created by cgo anyhow.

I can't reproduce the problem since I'm not on Darwin. All I know about it is in this issue: pebbe/zmq4#97

So right now it appears that nobody can reproduce the problem. And I don't understand how it could happen. We're not going to be able to fix this without a test case.

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)