If basicNode isn't the only struct that could be passed, I would argue that that's cleaner than checking for every possible type. Also doing it that way means that your interface couldn't care less about the actual structure of the struct and so is much more flexible. And they won't break if and when you decide to change the struct layout cause that doesn't matter anymore.
btw if the structs and interface are in different packages, you need to make those methods public or it wouldn't be able to call them. Can I suggest you join the golang discord chat server? You seem to be asking a lot of short answer questions and a chat server would give you faster response time than a forum. https://discord.gg/7WhXAaF On Wednesday, 2 May 2018 11:49:03 UTC+8, Mark Nahabedian wrote: > > Thanks for your help and patience Alex. I guess I need to do something > like > > https://play.golang.org/p/qURVD3of5oU > > but I find it kind of unclean to have to add private methods to do this. > > It wouldn't be appropriate to define a basicNode getter method on the node > interface since basicNode is just one possible implementstion. > > Anyway, I'm past that problem. > > Thank you. > -- 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 golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
