Re:Things I Wish Someone Had Told Me About Go
by matthavener on Monday March 11, 2013 @12:12PM
(#5357644)
I didn't quite "get" the point of the pointer/copy option on interfaces, but this makes it crystal clear. This works around such a common problem in writing C++ templates (which is really the only equivalent polymorphism if you want to dispatch a function on a native type):
template <class T> void doSomething(const T &expensiveCopy);
Versus: template <class T> void doSomething(T cheapCopy);
As usual, boost provides another crazy template hack to work around this issue:
Re:Things I Wish Someone Had Told Me About Go
by esrauch on Monday March 11, 2013 @11:15PM
(#5359868)
Can you explain why this is actually a problem? Why not just always have a const T&, is there some negative in the "cheap copy" case to not copy?
Re:Things I Wish Someone Had Told Me About Go
by matthavener on Tuesday March 12, 2013 @09:59AM
(#5361801)
I'm making some assumptions about the compiler optimization: If T is something like "int", then passing by reference can be more costly, because a value that was once stored in a register now needs a real memory address and must be deferenced to read.
Interface Pointers
Note that the author of a type that fulfills an interface and the consumer of a function that takes an interface both have full control over how much data is copied on a call to the function. You can control whether a type fulfills an interface, or whether a pointer to the type fulfills the interface. In Go, it is always easy to tell how much memory is being copied for any function call.