Searched refs:visibility (Results 1 – 10 of 10) sorted by relevance
41 …visibility: ["//tools/platform-compat/javatest/android/processor/compat/changeid:__subpackages__"],59 visibility: [
36 …visibility: ["//tools/platform-compat/javatest/android/processor/compat/unsupportedappusage:__subp…52 visibility: [
40 visibility: ["//libcore:__pkg__"],
35 visibility: ["//tools/platform-compat/java/android/processor/compat:__subpackages__"],
298 u1 visibility; member
266 dex::u1 visibility; member
323 ir_annotation->visibility = dexAnnotationItem->visibility; in ExtractAnnotationItem()568 ir_annotation->visibility = dex::kVisibilityEncoded; in ParseAnnotation()
441 if (ir_node->visibility != dex::kVisibilityEncoded) { in CreateAnnItemSection()647 SLICER_CHECK(ir_annotation->visibility != dex::kVisibilityEncoded); in WriteAnnotationItem()651 data.Push<dex::u1>(ir_annotation->visibility); in WriteAnnotationItem()
299 from the support library, where you can express the intended visibility if the300 method had not required visibility for testing, then metalava will treat that301 method using the intended visibility instead when generating signature files
META-INF/ META-INF/MANIFEST.MF jline/ jline/CompletionHandler.class CompletionHandler ...