Orthogonality means (roughly) "independent" in this context. I do agree with you, though, that the slide is incorrect. The spec <https://golang.org/ref/spec> defines type literals in the TypeLit production (search in page), which clearly only refers to composite types. The slides shouldn't talk about type literals, but only about "type", which is, how it's refered to in the spec under "Type declarations <https://golang.org/ref/spec#Type_declarations>"
On Wed, Jul 5, 2017 at 11:39 AM, Darren Hoo <darren....@gmail.com> wrote: > > > On Wed, Jul 5, 2017 at 5:27 PM, Jan Mercl <0xj...@gmail.com> wrote: > >> On Wed, Jul 5, 2017 at 11:03 AM Darren Hoo <darren....@gmail.com> wrote: >> >> >>> what is the relation between `type literal` and `named type`, >> >> >> >> Orthogonality. >> > >> > Then `int` is not named type. >> >> Please explain why do you think so. I don't get it. >> > > In https://talks.golang.org/2015/tricks.slide#5 says int is type > literal, then you say int is named type. > > How can int be both type literal and named type while they are orthogonal? > > Can you explain orthogonality for me? Thanks! > > -- > 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. > -- 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.
