On 05/29/2017 04:44 PM, Darko Luketic wrote:
>
> Ayan, no that's alright it was storage.UserModelInterface and I know
> what you're all saying but I saw no other way to make them type
> agnostic and I'm a fan of explicitly calling things what they are
> especially when I'm experimenting. And
Before we put the focus on criticism of the OP's code organisation, it's
well worth investigating the likely code bug first.
>but when I use var m storage.ModelInterface and then call a member
function of the interface (SetName) Go panics because nil pointer
dereference
Based on this problem descr
