You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug appears to be known but I couldn't find a corresponding github issue.
When grepping the resulting binary, the type of a in the above program appears to be recorded as chan (<-chan main.StandsOut), so the solution might be as simple as building additional parentheses around typ.string() in the implementation of reflect.ChanOf whenever the outer chan is BothDir and the inner chan is RecvDir.
I'll try to fix it.
The text was updated successfully, but these errors were encountered:
so the solution might be as simple as building additional parentheses around typ.string() in the implementation of reflect.ChanOf whenever the outer chan is BothDir and the inner chan is RecvDir.
The existing implementation of ChanOf omits the parentheses when
building the type string for channel types of the form
chan (<-chan T), so add them.
Fixesgolang#39897
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
It does on go1.14, haven't checked the most recent minor release.
What operating system and processor architecture are you using (
go env
)?go env
Output(redacted some stuff)
What did you do?
https://play.golang.org/p/YZG9p_qVnyC
What did you expect to see?
What did you see instead?
This bug appears to be known but I couldn't find a corresponding github issue.
When grepping the resulting binary, the type of
a
in the above program appears to be recorded aschan (<-chan main.StandsOut)
, so the solution might be as simple as building additional parentheses aroundtyp.string()
in the implementation ofreflect.ChanOf
whenever the outer chan isBothDir
and the inner chan isRecvDir
.I'll try to fix it.
The text was updated successfully, but these errors were encountered: