Identifiers, Names and Scopes
Names in Scala identify types, values, methods, and classes which are collectively called entities. Names are introduced by definitions and declarations, inheritance, import clauses, or package clauses which are collectively called bindings.
Bindings of each kind are assigned a precedence which determines whether one binding can shadow another:
- Definitions and declarations in lexical scope that are not top-level have the highest precedence.
- Definitions and declarations that are either inherited, or made available by a package clause and also defined in the same compilation unit as the reference to them, have the next highest precedence.
- Explicit imports have the next highest precedence.
- Wildcard imports have the next highest precedence.
- Bindings made available by a package clause, but not also defined in the same compilation unit as the reference to them, as well as bindings supplied by the compiler but not explicitly written in source code, have the lowest precedence.
There are two different name spaces, one for types and one for terms. The same name may designate a type and a term, depending on the context where the name is used.
A binding has a scope in which the entity defined by a single name can be accessed using a simple name. Scopes are nested. A binding in some inner scope shadows bindings of lower precedence in the same scope as well as bindings of the same or lower precedence in outer scopes.
Note that shadowing is only a partial order. In the following example,
neither binding of
x shadows the other. Consequently, the
x in the last line of the block is ambiguous.
A reference to an unqualified (type- or term-) identifier ´x´ is bound by the unique binding, which
- defines an entity with name ´x´ in the same namespace as the identifier, and
- shadows all other bindings that define entities with name ´x´ in that namespace.
It is an error if no such binding exists. If ´x´ is bound by an import clause, then the simple name ´x´ is taken to be equivalent to the qualified name to which ´x´ is mapped by the import clause. If ´x´ is bound by a definition or declaration, then ´x´ refers to the entity introduced by that binding. In that case, the type of ´x´ is the type of the referenced entity.
A reference to a qualified (type- or term-) identifier ´e.x´ refers to the member of the type ´T´ of ´e´ which has the name ´x´ in the same namespace as the identifier. It is an error if ´T´ is not a value type. The type of ´e.x´ is the member type of the referenced entity in ´T´.
Binding precedence implies that the way source is bundled in files affects name resolution. In particular, imported names have higher precedence than names, defined in other files, that might otherwise be visible because they are defined in either the current package or an enclosing package.
Note that a binding introduced by a packaging is taken as lowest precedence, since packages are open and can be defined across arbitrary compilation units.
The compiler supplies bindings from well-known packages and objects, called "root contexts". The standard locations for these bindings are:
- The object
- The package
- The package
These bindings are taken as lowest precedence, so that they are always shadowed by user code, which may contain competing imports and definitions.
A binding is available from a root context if it would also be available using an ordinary import clause. In particular, ordinary access restrictions apply.
A binding from an earlier root context shadows a binding of the same name from a later one.
java.lang.String, for which it is a type alias.
Multiple binding of a type identifier to the same underlying type is permitted. This is possible when import clauses introduce a binding of a member type alias with the same binding precedence, typically through wildcard imports. This allows redundant type aliases to be imported without introducing an ambiguity.
Similarly, imported aliases of names introduced by package statements are permitted:
Assume the following two definitions of objects named
X in packages
in separate compilation units.
The following program illustrates different kinds of bindings and precedences between them.