• Home
  • Raw
  • Download

Lines Matching refs:a

9    through Android P. Note that this isn't actually a single format; it evolved
10 over time, so older signature files vary a bit (many of these changes were
18 values, as well as cleans up a number of things (such as dropping
21 3. This is format v2, but with all nullness annotations replaced by a
31 to a new format?
35 annotations) be a formal part of the SDK.
40 changes. (For example, you can change the return value of a final method from
55 New signature files (v2+) generally include a file header comment which states
99 As a special optimization, since we eventually want **all** APIs to have
265 Kotlin's Java support means that it wil take a Kotlin property and compile it
291 Kotlin supports default values for parameters, and these are a part of the API
304 annotations to mark up the null contract for an element, we will also have a
305 special annotation to explicitly name a Java parameter:
322 also be part of the v2 signature since (as an example) removing a default value
323 is a compile-incompatible change.
333 for Java, just as with parameter names, you can specify a special annotation to
344 Consider a scenario where a public class extends a hidden class, and that hidden
345 class defines a public method.
353 this happens is that StringBuilder is a public class which extends hidden class
389 The old signature file format used "deprecated" as if it was a modifier. In the
394 Doclava had a "random" (but stable) order of modifiers.
417 In "extends" lists, the signature file can list a comma separated list of
429 We have a number of annotations which are significant for the API -- not just
443 case of Kotlin code, a special JetBrains nullness annotation), or the one that
485 If a method overrides another method, and the signatures are the same, 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
492 In v2, we take this one step further: If a method differs **only** from its
502 indentation; this is probably just a bug. The new format aligns their
512 the previous API levels. Metalava can regenerate these for a new format.