Lines Matching refs:from

11    due to bugs getting fixed, such as type parameters missing from classes
30 Why did we change from the historical doclava signature format (v1)
40 changes. (For example, you can change the return value of a final method from
157 With these changes, these lines from v1 signature files:
181 in the above it was missing from super interface Collection:
266 into getters and setters which you can call from Java. But you cannot calls
267 these getters and setters from Kotlin; you **must** use the property
284 The last two elements are "redundant"; they could be computed from the property
286 the getters and setters away from the defaults), but it's helpful to be explicit
307 from Java, but Kotlin client code can now reference the parameter.
334 record the default value for usage from languages that support default parameter
466 classes from java.lang that are used in lots of places in the signature file
471 This basically builds on the same idea from having an implicit package for
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