Status Update
Comments
al...@google.com <al...@google.com>
tn...@google.com <tn...@google.com> #2
I think this basically requires us to solve type use annotations -- this is basically annotating a type. You could use that annotated type inside another type (List<BundledSQLiteStatement>>) etc.
da...@google.com <da...@google.com> #3
I ran into this issue again, this time the IDE is warning me that the 'actual' declaration is missing the @RestricTo
annotation the 'expect' declaration has, but I can't add it. :'(
ja...@gmail.com <ja...@gmail.com> #4
Hello. Is there any news on this - is it not a case of adding AnnotationTarget.TYPEALIAS
?
ju...@google.com <ju...@google.com> #5
Isn't @RestrictTo class Foo
, wouldn't we want to prevent usage of List<Foo>
from outside the restricted scope? I'm guessing the lint check only does that indirectly by preventing Foo
's constructor from being called.
mg...@google.com <mg...@google.com> #6
We need RestrictTo
support for typealias
to migrate lifecycle.common
to KotlinTarget 2. See
Description
Could we please support
@RestrictTo
targeting type aliases?I would like to do:
but can't right because
AnnotationTarget.TYPEALIAS
is not one of the annotation targets of@RestricTo
.Ideally I would just make the typealiashttps://youtrack.jetbrains.com/issue/KT-37316 .
internal
but can't right now due to being an actual / expect class, see