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
The documentation for the VisibleForTesting documentation is unclear on what the intended behaviour should be for Kotlin code.
The documentation leads you to believe that a Kotlin public member annotated with @VisibleForTesting should otherwise be considered package-private; however, Kotlin has no package-private visibility, and the one-less-than-public visibility to apply is internal.
This makes the annotation useless in Kotlin code, because if it is enforced, it means you can't use annotated symbols in the internal scope, but you can use them in the narrower but inexistent package-private scope.
The text was updated successfully, but these errors were encountered:
The documentation for the
VisibleForTesting
documentation is unclear on what the intended behaviour should be for Kotlin code.The documentation leads you to believe that a Kotlin public member annotated with
@VisibleForTesting
should otherwise be considered package-private; however, Kotlin has no package-private visibility, and the one-less-than-public visibility to apply isinternal
.This makes the annotation useless in Kotlin code, because if it is enforced, it means you can't use annotated symbols in the
internal
scope, but you can use them in the narrower but inexistent package-private scope.The text was updated successfully, but these errors were encountered: