diff --git a/docs/docs/reference/changed/implicit-conversions.md b/docs/docs/reference/changed/implicit-conversions.md index f017a78a9d14..f5c78d1ef262 100644 --- a/docs/docs/reference/changed/implicit-conversions.md +++ b/docs/docs/reference/changed/implicit-conversions.md @@ -31,16 +31,16 @@ its type checking because this turns out to be more efficient). In summary, previous code using implicit conversion parameters such as - def useConversion(implicit f: A => B) { + def useConversion(implicit f: A => B) = { val y: A = ... val x: B = a // error under Dotty } is no longer legal and has to be rewritten to - def useConversion(implicit f: ImplicitConverter[A, B]) { + def useConversion(implicit f: ImplicitConverter[A, B]) = { val y: A = ... - val x: B = a // OK + val x: B = y // OK } ### Reference diff --git a/docs/docs/reference/changed/implicit-resolution.md b/docs/docs/reference/changed/implicit-resolution.md index f35e60e9ed8d..8fa6eca24709 100644 --- a/docs/docs/reference/changed/implicit-resolution.md +++ b/docs/docs/reference/changed/implicit-resolution.md @@ -4,7 +4,7 @@ title: "Changes in Implicit Resolution" --- Implicit resolution uses a new algorithm which caches implicit results -more aggressively for perforance. There are also some changes that +more aggressively for performance. There are also some changes that affect implicits on the language level. 1. Types of implicit values and result types of implicit methods