Lines Matching refs:which

16 2. The "new" format, which is described below, and is used in Android Q. This
55 New signature files (v2+) generally include a file header comment which states
72 @Override etc); only those which are significant for the API, such as nullness
266 into getters and setters which you can call from Java. But you cannot calls
306 @android.annotation.ParameterName (which is hidden). This obviously isn't usable
353 this happens is that StringBuilder is a public class which extends hidden class
354 AbstractStringBuilder, which defines the public method setLength.
411 The above list doesn't include the Kotlin modifiers, which are inserted
429 We have a number of annotations which are significant for the API -- not just
430 the nullness as deprecation ones (which are specially supported in v3 via the
441 That begs the question: which fully qualified name should we put in the
442 signature file? The one that appeared in the source (which is hidden, or in the
480 In v3, "type use annotations" are supported which means annotations can appear