package annotation
- Alphabetic
- Public
- All
Type Members
-
abstract
class
Annotation extends AnyRef
A base class for annotations.
A base class for annotations. Annotations extending this class directly are not preserved for the Scala type checker and are also not stored as Java annotations in classfiles. To enable either or both of these, one needs to inherit from scala.annotation.StaticAnnotation or/and scala.annotation.ClassfileAnnotation.
- Since
2.4
-
trait
ClassfileAnnotation extends Annotation with StaticAnnotation
A base class for classfile annotations.
A base class for classfile annotations. These are stored as Java annotations] in classfiles.
- Since
2.4
-
trait
StaticAnnotation extends Annotation
A base class for static annotations.
A base class for static annotations. These are available to the Scala type checker, even across different compilation units.
- Since
2.4
-
trait
TypeConstraint extends Annotation
A marker for annotations that, when applied to a type, should be treated as a constraint on the annotated type.
A marker for annotations that, when applied to a type, should be treated as a constraint on the annotated type.
A proper constraint should restrict the type based only on information mentioned within the type. A Scala compiler can use this assumption to rewrite the contents of the constraint as necessary. To contrast, a type annotation whose meaning depends on the context where it is written down is not a proper constrained type, and this marker should not be applied. A Scala compiler will drop such annotations in cases where it would rewrite a type constraint.
- Since
2.6
-
final
class
compileTimeOnly extends Annotation with StaticAnnotation
An annotation that designates that an annottee should not be referred to after type checking (which includes macro expansion).
An annotation that designates that an annottee should not be referred to after type checking (which includes macro expansion).
Examples of potential use: 1) The annottee can only appear in the arguments of some other macro that will eliminate it from the AST during expansion. 2) The annottee is a macro and should have been expanded away, so if hasn't, something wrong has happened. (Comes in handy to provide better support for new macro flavors, e.g. macro annotations, that can't be expanded by the vanilla compiler).
- Annotations
- @getter() @setter() @beanGetter() @beanSetter() @companionClass() @companionMethod()
- Since
2.11.0
-
final
class
elidable extends Annotation with StaticAnnotation
An annotation for methods whose bodies may be excluded from compiler-generated bytecode.
An annotation for methods whose bodies may be excluded from compiler-generated bytecode.
Behavior is influenced by passing
-Xelide-below <arg>
toscalac
. Calls to methods marked elidable (as well as the method body) will be omitted from generated code if the priority given the annotation is lower than that given on the command line.@elidable(123) // annotation priority scalac -Xelide-below 456 // command line priority
The method call will be replaced with an expression which depends on the type of the elided expression. In decreasing order of precedence:
Unit () Boolean false T <: AnyVal 0 T >: Null null T >: Nothing Predef.???
Complete example:
import scala.annotation._, elidable._ object Test extends App { def expensiveComputation(): Int = { Thread.sleep(1000) ; 172 } @elidable(WARNING) def warning(msg: String) = println(msg) @elidable(FINE) def debug(msg: String) = println(msg) @elidable(FINE) def computedValue = expensiveComputation() warning("Warning! Danger! Warning!") debug("Debug! Danger! Debug!") println("I computed a value: " + computedValue) } % scalac example.scala && scala Test Warning! Danger! Warning! Debug! Danger! Debug! I computed a value: 172 // INFO lies between WARNING and FINE % scalac -Xelide-below INFO example.scala && scala Test Warning! Danger! Warning! I computed a value: 0
- Since
2.8
-
final
class
implicitAmbiguous extends Annotation with StaticAnnotation
To customize the error message that's emitted when an implicit search finds multiple ambiguous values, annotate at least one of the implicit values
@implicitAmbiguous
.To customize the error message that's emitted when an implicit search finds multiple ambiguous values, annotate at least one of the implicit values
@implicitAmbiguous
. Assuming the implicit value is a method with type parametersX1,..., XN
, the error message will be the result of replacing all occurrences of${Xi}
in the stringmsg
with the string representation of the corresponding type argumentTi
.If more than one
@implicitAmbiguous
annotation is collected, the compiler is free to pick any of them to display.Nice errors can direct users to fix imports or even tell them why code intentionally doesn't compile.
trait =!=[C, D] implicit def neq[E, F] : E =!= F = null @annotation.implicitAmbiguous("Could not prove ${J} =!= ${J}") implicit def neqAmbig1[G, H, J] : J =!= J = null implicit def neqAmbig2[I] : I =!= I = null implicitly[Int =!= Int]
- Annotations
- @getter()
- Since
2.12.0
-
final
class
implicitNotFound extends Annotation with StaticAnnotation
To customize the error message that's emitted when an implicit of type C[T1,..., TN] cannot be found, annotate the class C with @implicitNotFound.
To customize the error message that's emitted when an implicit of type C[T1,..., TN] cannot be found, annotate the class C with @implicitNotFound. Assuming C has type parameters X1,..., XN, the error message will be the result of replacing all occurrences of ${Xi} in the string msg with the string representation of the corresponding type argument Ti. *
- Since
2.8.1
-
class
nowarn extends Annotation with ClassfileAnnotation
An annotation for local warning suppression.
An annotation for local warning suppression.
The optional
value
parameter allows selectively silencing messages, seescalac -Wconf:help
for help. Examples:def f = { 1: @nowarn // don't warn "a pure expression does nothing in statement position" 2 } @nowarn def f = { 1; deprecated() } // don't warn @nowarn("msg=pure expression does nothing") def f = { 1; deprecated() } // show deprecation warning
To ensure that a
@nowarn
annotation actually suppresses a warning, enable-Xlint:unused
or-Wunused:nowarn
.- Annotations
- @nowarn()
-
class
showAsInfix extends Annotation with StaticAnnotation
This annotation configures how Scala prints two-parameter generic types.
This annotation configures how Scala prints two-parameter generic types.
By default, types with symbolic names are printed infix; while types without them are printed using the regular generic type syntax.
Example of usage:
scala> class Map[T, U] defined class Map scala> def foo: Int Map Int = ??? foo: Map[Int,Int] scala> @showAsInfix class Map[T, U] defined class Map scala> def foo: Int Map Int = ??? foo: Int Map Int
- Since
2.12.2
-
class
strictfp extends Annotation with StaticAnnotation
If this annotation is present on a method or its enclosing class, the strictfp flag will be emitted.
If this annotation is present on a method or its enclosing class, the strictfp flag will be emitted.
- Since
2.9
-
final
class
switch extends Annotation with StaticAnnotation
An annotation to be applied to a match expression.
An annotation to be applied to a match expression. If present, the compiler will verify that the match has been compiled to a tableswitch or lookupswitch and issue an error if it instead compiles into a series of conditional expressions. Example usage:
val Constant = 'Q' def tokenMe(ch: Char) = (ch: @switch) match { case ' ' | '\t' | '\n' => 1 case 'A' | 'Z' | '$' => 2 case '5' | Constant => 3 // a non-literal may prevent switch generation: this would not compile case _ => 4 }
Note: for pattern matches with one or two cases, the compiler generates jump instructions. Annotating such a match with
@switch
does not issue any warning.- Since
2.8
-
final
class
tailrec extends Annotation with StaticAnnotation
A method annotation which verifies that the method will be compiled with tail call optimization.
A method annotation which verifies that the method will be compiled with tail call optimization.
If it is present, the compiler will issue an error if the method cannot be optimized into a loop.
- Since
2.8
-
class
unspecialized extends Annotation with StaticAnnotation
A method annotation which suppresses the creation of additional specialized forms based on enclosing specialized type parameters.
A method annotation which suppresses the creation of additional specialized forms based on enclosing specialized type parameters.
- Since
2.10
-
final
class
varargs extends Annotation with StaticAnnotation
A method annotation which instructs the compiler to generate a Java varargs-style forwarder method for interop.
A method annotation which instructs the compiler to generate a Java varargs-style forwarder method for interop. This annotation can only be applied to methods with repeated parameters.
- Since
2.9
Value Members
-
object
elidable
This useless appearing code was necessary to allow people to use named constants for the elidable annotation.
This useless appearing code was necessary to allow people to use named constants for the elidable annotation. This is what it takes to convince the compiler to fold the constants: otherwise when it's time to check an elision level it's staring at a tree like
(Select(Level, Select(FINEST, Apply(intValue, Nil))))
instead of the number
300
.- Since
2.8
This is the documentation for the Scala standard library.
Package structure
The scala package contains core types like
Int
,Float
,Array
orOption
which are accessible in all Scala compilation units without explicit qualification or imports.Notable packages include:
scala.collection
and its sub-packages contain Scala's collections frameworkscala.collection.immutable
- Immutable, sequential data-structures such asVector
,List
,Range
,HashMap
orHashSet
scala.collection.mutable
- Mutable, sequential data-structures such asArrayBuffer
,StringBuilder
,HashMap
orHashSet
scala.collection.concurrent
- Mutable, concurrent data-structures such asTrieMap
scala.collection.parallel.immutable
- Immutable, parallel data-structures such asParVector
,ParRange
,ParHashMap
orParHashSet
scala.collection.parallel.mutable
- Mutable, parallel data-structures such asParArray
,ParHashMap
,ParTrieMap
orParHashSet
scala.concurrent
- Primitives for concurrent programming such asFutures
andPromises
scala.io
- Input and output operationsscala.math
- Basic math functions and additional numeric types likeBigInt
andBigDecimal
scala.sys
- Interaction with other processes and the operating systemscala.util.matching
- Regular expressionsOther packages exist. See the complete list on the right.
Additional parts of the standard library are shipped as separate libraries. These include:
scala.reflect
- Scala's reflection API (scala-reflect.jar)scala.xml
- XML parsing, manipulation, and serialization (scala-xml.jar)scala.swing
- A convenient wrapper around Java's GUI framework called Swing (scala-swing.jar)scala.util.parsing
- Parser combinators (scala-parser-combinators.jar)Automatic imports
Identifiers in the scala package and the
scala.Predef
object are always in scope by default.Some of these identifiers are type aliases provided as shortcuts to commonly used classes. For example,
List
is an alias forscala.collection.immutable.List
.Other aliases refer to classes provided by the underlying platform. For example, on the JVM,
String
is an alias forjava.lang.String
.