You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Without the `@unchecked` annotation, a Scala compiler could infer that the pattern match is non-exhaustive, and could produce a warning because `Option` is a `sealed` class.
88
88
89
-
*`@uncheckedStable` When applied a value definition, it allows the defined value to appear in a path, even if its type is [volatile](03-types.html#volatile-types).
89
+
*`@uncheckedStable` When applied to a value definition, it allows the defined value to appear in a path, even if its type is [volatile](03-types.html#volatile-types).
90
90
For instance, the following member definitions are legal:
91
91
```scala
92
92
typeA { typeT }
@@ -97,7 +97,7 @@ val y: x.T // OK since `x' is still a path
97
97
Without the `@uncheckedStable` annotation, the designator `x` would not be a path since its type `A with B` is volatile.
98
98
Hence, the reference `x.T` would be malformed.
99
99
100
-
When applied to value definitions that have non-volatile types, the annotation has no effect.
100
+
When applied to value definitions that have no volatile types, the annotation has no effect.
101
101
102
102
*`@specialized` When applied to the definition of a type parameter, this annotation causes the compiler to generate specialized definitions for primitive types.
103
103
An optional list of primitive types may be given, in which case specialization takes into account only those types.
0 commit comments