Skip to content

Commit

Permalink
Fix typo and example code
Browse files Browse the repository at this point in the history
  • Loading branch information
odersky committed Feb 1, 2019
1 parent a1ffafc commit 5f37755
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion docs/docs/reference/contextual/conversions.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ An implicit conversion is applied automatically by the compiler in three situati

1. If an expression `e` has type `T`, and `T` does not conform to the expression's expected type `S`.
2. In a selection `e.m` with `e` of type `T`, but `T` defines no member `m`.
3. In an application `e.m(args)` with `e` of type `T`, if ``T` does define
3. In an application `e.m(args)` with `e` of type `T`, if `T` does define
some member(s) named `m`, but none of these members can be applied to the arguments `args`.

In the first case, the compiler looks in the implied scope for a an instance of
Expand Down
2 changes: 1 addition & 1 deletion docs/docs/reference/contextual/instance-defs.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ The name of an implied instance can be left out. So the implied instance definit
of the last section can also be expressed like this:
```scala
implied for Ord[Int] { ... }
implied [T: Ord] for Ord[List[T]] { ... }
implied [T] given (ord: Ord[T]) for Ord[List[T]] { ... }
```
If the name of an instance is missing, the compiler will synthesize a name from
the type(s) in the `for` clause.
Expand Down

0 comments on commit 5f37755

Please sign in to comment.