From 7e63704ebbdda92e52ad3fa6e6e50525e49c0839 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jakub=20Koz=C5=82owski?= Date: Thu, 8 Dec 2022 19:18:01 +0100 Subject: [PATCH] Use more precise explanation for opaque transparency --- docs/_docs/reference/other-new-features/opaques.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/_docs/reference/other-new-features/opaques.md b/docs/_docs/reference/other-new-features/opaques.md index b87d45485a93..d20e350ef940 100644 --- a/docs/_docs/reference/other-new-features/opaques.md +++ b/docs/_docs/reference/other-new-features/opaques.md @@ -174,6 +174,6 @@ val z = l2(3.1) l1.mul(x, y) // type checks l1.mul(x, z) // error: found l2.Logarithm, required l1.Logarithm ``` -In general, one can think of an opaque type as being only transparent in the scope of `private[this]`. +In general, one can think of an opaque type as being only transparent in the scope of `private[this]` (unless the type is a top level definition - in this case, it's transparent only within the file it's defined in). [More details](opaques-details.md)