> I believe at least for most cases, Henry's approach above is the correct solution, and this truly needs to be documented somewhere for further reference.
I thought about suggesting that, but I was assuming you where using a type definition because you wanted the types to be different (e.g. to put methods on it, or just for safety). -- 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 [email protected]. To view this discussion visit https://groups.google.com/d/msgid/golang-nuts/CAEkBMfFd4Q65xgWoON0Mpk_b2e30eoab-dMqc-QBsGi%2BBF3QrA%40mail.gmail.com.
