answered... This point of the language makes this design decision really
unclear when beginning. Because method calls on method receivers are
statically resolved, while method calls on arguments whose types are
interfaces are dynamically dispatched and statically checked (compile-time
error when the expected interface is not implemented). So this question
really needs more attention and a more straightforward design rule. Mix in
type embedding and you end up with a mental node ><
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firstname.lastname@example.org.
For more options, visit https://groups.google.com/d/optout.