Lines Matching refs:is

14    containing class is final.
16 2. The "new" format, which is described below, and is used in Android Q. This
21 3. This is format v2, but with all nullness annotations replaced by a
38 that we can not just record explicitly what the API contract is, but also
66 Here "2" is the major format version; the .0 allows for compatible minor
141 The above signature line is turned into
152 structure in the signature file. For example, in v1, an interface is called an
153 "abstract interface"; an interface extending another interface is said to
306 @android.annotation.ParameterName (which is hidden). This obviously isn't usable
323 is a compile-incompatible change.
351 An example of this is StringBuilder#setLength. According to the old signature
353 this happens is that StringBuilder is a public class which extends hidden class
397 and Kotlin, wihch more closely mirrors what is done in the source code.
424 extends Object>. These are equivalent. In the v2 format, <? extends Object> is
442 signature file? The one that appeared in the source (which is hidden, or in the
467 (java.lang.String alone is present in over 11,000 lines of the API file), and
486 overriding method is left out of the signature file. This basically compares the
488 also that some modifiers are implicit; for example, if a method is implementing
489 a method from an interface, the interface method is implicitly abstract, so the
493 overridden method by "final", **and** if the containing class is final, then the
494 method is not included in the signature file. The same is the case for
502     indentation; this is probably just a bug. The new format aligns their