On this page
Object elidable.elidable
object elidable
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
.
Supertypes | |
---|---|
Self type |
Concrete fields
Source
final val ALL: -2147483648
The levels ALL
and OFF
are confusing in this context because the sentiment being expressed when using the annotation is at cross purposes with the one being expressed via -Xelide-below
. This confusion reaches its zenith at level OFF
, where the annotation means never elide this method but -Xelide-below OFF
is how you would say elide everything possible.
With no simple remedy at hand, the issue is now at least documented, and aliases MAXIMUM
and MINIMUM
are offered.
Source
final val ASSERTION: 2000
Source
final val CONFIG: 700
Source
final val FINE: 500
Source
final val FINER: 400
Source
final val FINEST: 300
Source
final val INFO: 800
Source
final val MAXIMUM: 2147483647
Source
final val MINIMUM: -2147483648
Source
final val OFF: 2147483647
Source
final val SEVERE: 1000
Source
final val WARNING: 900
Source
© 2002-2022 EPFL, with contributions from Lightbend.
Licensed under the Apache License, Version 2.0.
https://scala-lang.org/api/3.2.0/scala/annotation/elidable$.html