This article will introduce keywords and identifiers in Go.
Keywords are the special words which help compilers understand and parse user code.Up to now (Go 1.13), Go has only 25 keywords:
They can be categorized as four groups:
break default func interface select case defer go map struct chan else goto package switch const fallthrough if range type continue for import return var
varare used to declare all kinds of code elements in Go programs.
structare used as parts in some composite type denotations.
switchare used to control flow of code.
goare also control flow keywords, but in other specific manners. They modify function calls, which we'll talk about in this article.
These keywords will be explained in details in other articles.
_(underscore), and start with either an Unicode letter or
keywords can not be used as identifiers.
_ is a special identifier, it is called blank identifier.
Later we will learn that all names of types, variables, constants, labels, package names and package import names must be identifiers.
An identifier starting with an Unicode upper case letter is called an exported identifier. The word exported can be interpreted as public in many other languages. The identifiers which don't start with an Unicode upper case letter are called non-exported identifiers. The word non-exported can be interpreted as private in many other languages. Currently (Go 1.13), eastern characters are viewed as non-exported letters. Sometimes, non-exported identifiers are also called unexported identifiers.
Here are some legal non-exported identifiers:
Player_9 DoSomething VERSION Ĝo Π
And here are some tokens which are illegal to be used as identifiers:
_ _status memStat book π 一个类型 변수 エラー
// Starting with a Unicode digit. 123 3apples // Containing Unicode characters not // satisfying the requirements. a.b *ptr $name firstname.lastname@example.org // These are keywords. type range
The Go 101 project is hosted on Github. Welcome to improve Go 101 articles by submitting corrections for all kinds of mistakes, such as typos, grammar errors, wording inaccuracies, description flaws, code bugs and broken links.
If you would like to learn some Go details and facts every serveral days, please follow Go 101's official Twitter account: @go100and1.