[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 08/24] golang/xenlight: define Mac builtin type
> What's the point of this? > > I realize it's slightly annoying to have to type `mac[0], mac[1], ...`, > but I'd rather do that once than make the runtime copy everything over > into a slice of interfaces every String() call. As I think you realized by looking at subsequent patches, this is to get around the fact that "an array of an interface type != an array of type that implements that interface." Since this is a small array, I'm fine with explicitly passing each element of the array to fmt.Sprintf. > Also, I guess the format should be "%02x". Yeah, thanks. > Conversely, shouldn't this be a value receiver, since we're don't want > this function to change the contents of mac? Conventionally receivers are kept consistent between methods of a type, unless it's implementing some interface like Stringer. And, it's consistent with the other toC functions which are defined with pointers in the generated functions since there are some large structs. But, yes this could just be a value receiver. I don't have a strong opinion to keep it as is, so I'll change it. -NR _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |