runtime: how should a nil go or nil defer behave?

[randall77]

go ((func())(nil))()

Should it panic in the calling go routine, or at the start of the called goroutine?

    defer ((func())(nil))()

Should it panic at the defer statement, or at the return point?

We've had some argument either way.  Panicing in the calling goroutine / at defer
statement is failing early, might be useful for people.  Panicing late might be
expected, as the go/deferred routine doesn't actually use the nil value until then.

Panicing late is what we do now.

The runtime meeting decided gri should figure this out, maybe update the spec.

Related to issues 8045 (go) and 8047 (defers).

[griesemer]

Comment 1:

Status changed to Duplicate.

Merged into issue #8107.