Skip to content

Commit 9f9bb0b

Browse files
som-snyttWojciechMazur
authored andcommitted
Preliminary ported edits
[Cherry-picked 11eff96]
1 parent 2c8e323 commit 9f9bb0b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/_spec/11-annotations.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ Here, ´c´ is a constructor of a class ´C´, which must conform to the class `
2020
Annotations may apply to definitions, types, or expressions.
2121
An annotation of a definition appears in front of that definition.
2222
An annotation of a type appears after that type.
23-
An annotation of an expression ´e´ appears after the expression ´e´, separated by a colon.
23+
An annotation of an expression appears after that expression, separated by a colon.
2424
More than one annotation clause may apply to an entity.
2525
The order in which these annotations are given does not matter.
2626

@@ -86,7 +86,7 @@ def f(x: Option[Int]) = (x: @unchecked) match {
8686
```
8787
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.
8888

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).
9090
For instance, the following member definitions are legal:
9191
```scala
9292
type A { type T }
@@ -97,7 +97,7 @@ val y: x.T // OK since `x' is still a path
9797
Without the `@uncheckedStable` annotation, the designator `x` would not be a path since its type `A with B` is volatile.
9898
Hence, the reference `x.T` would be malformed.
9999

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.
101101

102102
* `@specialized` When applied to the definition of a type parameter, this annotation causes the compiler to generate specialized definitions for primitive types.
103103
An optional list of primitive types may be given, in which case specialization takes into account only those types.

0 commit comments

Comments
 (0)