Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
tree: 5b9d10224c
Fetching contributors…

Cannot retrieve contributors at this time

61 lines (53 sloc) 2.269 kb
\begin{Exercise}[title={Method calls},difficulty=2]
\Question \label{ex:methodcalls q1} Suppose we have the following
program. Note the package \package{container/vector} was once part
of Go, but has been removed when the \func{append} built-in was introduced.
However, for this question this isn't important. The package implemented
a stack-like structure, with push and pop methods.
package main
import "container/vector"
func main() {
k1 := vector.IntVector{}
k2 := &vector.IntVector{}
k3 := new(vector.IntVector)
What are the types of \var{k1}, \var{k2} and \var{k3}?
\Question Now, this program compiles and runs OK. All the \func{Push}
operations work even though the variables are of a different type. The
documentation for \func{Push} says:
func (p *IntVector) Push(x int)
Push appends x to the end of the vector.
So the receiver has to be of type \type{*IntVector}, why does the code
above (the Push statements) work correct then?
\Question The type of \var{k1} is \type{vector.IntVector}. Why? We use
a composite literal (the \verb|{}|), so we get a value of that type
back. The variable \var{k2} is of \type{*vector.IntVector}, because we
take the address (\verb|&|) of the composite literal. And finally
\var{k3} has also the type \type{*vector.IntVector}, because \func{new}
returns a pointer to the type.
\Question The answer is given in \cite{go_spec} in the section ``Calls'',
where among other things it says:
A method call \func{x.m()} is valid if the method set of (the type of)
contains \func{m} and the argument list can be assigned to the parameter list
of \func{m}. If \var{x} is addressable and \var{\&x}'s method set
contains \func{m}, \func{x.m()} is shorthand for \func{(\&x).m()}.
In other words because \var{k1} is addressable and
\type{*vector.IntVector} \emph{does} have the \func{Push} method, the
call \lstinline{k1.Push(2)} is translated by Go into
\lstinline{(&k1).Push(2)} which makes the type system happy again (and
you too --- now you know this).\footnote{Also see section
``\titleref{sec:methods}'' in this chapter.}
Jump to Line
Something went wrong with that request. Please try again.