Since there wasn't an obvious EOF passed through, or another form of special error. Header couldn't be made nil as it was publicly exposed and would constitute a signature change.
This does however introduce a behaviour change. message.Read can no return nil. Didn't seem to impact tests will probably impact users
Since there wasn't an obvious EOF passed through, or another form of special error. Header couldn't be made nil as it was publicly exposed and would constitute a signature change.
This does however introduce a behaviour change.
message.Readcan no return nil. Didn't seem to impact tests will probably impact users