On Mon, Mar 4, 2019 at 8:00 AM Michel Levieux <m.levi...@capitaldata.fr> wrote: > > I just have a little question here: sometimes reading the low-level code of > Go (like runtime, compiler code etc) I find the names of structs and fields > quite hard to understand, like acronyms or abreviations or even initials that > are not very common, and can't seem to find why it's this way. Can anyone > explain this to me or point me to documentation about that? Maybe it has to > do with binary sizes of go programs?
It's because the code was originally written in C and was then transcribed to Go while keeping the names the same. It doesn't have anything to do with program binary size (although that is an interesting thought and may be worth considering). I don't know of any general docs on the naming. If you want to ask about specific abbreviations, feel free to ask here and we will do our best. Ian -- 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.
