title: Idiomatic way of naming Getters in Go
body: <p>The Effective go has following advice on naming of getters:</p>
  
  <blockquote>
    <p>Go doesn't provide automatic support for getters and setters. There's
    nothing wrong with providing getters and setters yourself, and it's
    often appropriate to do so, but it's neither idiomatic nor necessary
    to put Get into the getter's name. If you have a field called owner
    (lower case, unexported), the getter method should be called Owner
    (upper case, exported), not GetOwner. The use of upper-case names for
    export provides the hook to discriminate the field from the method. A
    setter function, if needed, will likely be called SetOwner. Both names
    read well in practice:</p>
  </blockquote>
  
  <p>Source: <a href="https://golang.org/doc/effective_go.html#Getters" rel="nofollow noreferrer">https://golang.org/doc/effective_go.html#Getters</a></p>
  
  <p>Now, this advice doesn't seem to consistent as the stdlib itself violates this multiple times. 
  <a href="https://i.stack.imgur.com/t497e.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/t497e.png" alt="enter image description here"></a></p>
  
  <p>As you can see in above screenshot, there are multiple methods  which use GetX naming convention which is advised against in the effective go guide.</p>
  
  <p>So the question is is the advice given in guide wrong or these methods are named wrongly &amp; would be fixed in future versions?</p>