It means there is no specific type name, but the resultant type must either be bool or convertible to bool:
type A bool var n int var ok A n, ok = x.(int) Using bool here is not common, but you see this with int and float, etc. Untyped constants is one of the most prominent Go features. > On Nov 2, 2016, at 4: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 > <mailto:golang-nuts+unsubscr...@googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <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.
