net/http: Header.Clone behavior #33141
Closed
Milestone
Comments
Agree. Will send a change. |
Change https://golang.org/cl/188022 mentions this issue: |
This was referenced Oct 13, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
Header.Clone
method is being added in Go1.13. It's current behavior is to always allocate a map and return it even if the receiver is nil.Thus:
Is this behavior we want to go with? It seems more consistent for
Clone
to return nil if the receiver is also nil.The text was updated successfully, but these errors were encountered: