Be consistent with receiver type on method definitions #6165
Labels
needs discussion
Issues that need discussion before they can be worked on
type: code hygiene
Clean up code but without changing functionality or interfaces
Reference comment: #6103 (comment)
We should try and not mix and mash pointer-value receivers on methods and instead consistently use one or the other. For types that need mutations and already have a method that receives value as a pointer, rest of methods can be amended to change from a value receiver to a pointer.
For small types that don't have a pointer receiver currently and also aren't costly to pass around as args, we can stick with value receivers.
For Admin Use
The text was updated successfully, but these errors were encountered: