It's a constant literal until it's used in a typed context. This section explains it in detail:
https://golang.org/ref/spec#Constants On Wed, Nov 2, 2016 at 6:09 AM, Martin Steffen <martin.sput...@gmail.com> wrote: > Hi, in the language spec, e.g. in connection with ``type assertions'' and > ``special forms'', like > > v, ok = x.(T) > > it's stated that it yield (in ok) an additional value which is both untyped > and boolean > (an ``untyped boolean value''). > > How should one interpret that? If ok behaves like a boolean, why is it > considered as untyped? > > Martin > > > -- > 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. > -- gustavo @ http://niemeyer.net -- 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.
