Lines Matching refs:which

11   (which in turn get compiled into android.jar, the Android SDK library) and
17   the typedef annotations, which cannot be stored in the SDK as .class level
77 * Ability to read in an existing android.jar file instead of from source, which
80   methods which were accidentally not included.)
87 * Support for an updated signature file format (which is described in FORMAT.md)
89   * Address errors in the doclava1 format which for example was missing
148   recently changed and if so marking them as @Migrate (which lets the Kotlin
154   need to be able to figure out which parts of the source code is included in
155   the API and which one is implementation; it is simply handed the filtered API
169 * Consistent stubs: In doclava1, the code which iterated over the API and
176   public method inherited from a package protected super class, which the API
186   Some of these take advantage of looking at the source code which wasn't
189   class, which is forbidden.
191 * Baselines: Metalava can report all of its issues into a "baseline" file, which
200 * Metalava can generate reports about nullness annotation coverage (which helps
275   javadoc, which meant that most of the source tree was opaque. Therefore, as
276   just one example, the code which generated documentation for typedef constants
283   annotation files needed by Studio and lint in Gradle, which captures the
291   functionality is now rolled into metalava, which has one very important
294   doclava, which sometimes generated incorrect results. Metalava uses the
307 these are hidden behind a "model": an abstraction layer which only exposes high
320     to parse older source code which may no longer be easy to parse.
339 are hidden, which is why it's called a "Codebase" rather than an "API").
364 which limits itself to visiting code elements that are part of the API.
367 implemented: they simply extend `ApiVisitor`, which means they'll only export
392 There is a `TypeVisitor` similar to `ItemVisitor` which you can use to visit all
401 Another visitor which helps with implementation is the ComparisonVisitor:
444 in which case the deletion is allowed.))
449 files, which can then be processed by Dokka and Javadoc to generate the same
460 typedef macro), but should also help Dokka -- and arguably the Kotlin code which