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
The combination of the following CLs causing a nil panic:
CL/17873: make chained multiReader Read more efficient
CL/28533: make MultiReader nil exhausted Readers for earlier GC
The first CL allows MultiReader to "inherit" another MultiReader's list of io.Reader. This is problematic when combined with the later CL since that can set readers in that list to nil.
Suggested fix is to change= nil to = eofReader where eofReader is some pre-allocated reader that does the obvious thing. That will make sure the behavior of io.MultiReader(nil) does not change.
The combination of the following CLs causing a nil panic:
The first CL allows MultiReader to "inherit" another MultiReader's list of io.Reader. This is problematic when combined with the later CL since that can set readers in that list to nil.
Reproduction: https://play.golang.org/p/jPl_pRr3ul
Discussion: https://groups.google.com/forum/#!topic/golang-dev/a5K3132l3_E
\cc @rsc @bradfitz @ncw
The text was updated successfully, but these errors were encountered: