Searched refs:nullness (Results 1 – 11 of 11) sorted by relevance
| /tools/metalava/ |
| D | README.md | 103 API contract (in particular nullness contracts, as well as parameter names
106 * Support for a "compact" nullness format -- one based on Kotlin's
108 their nullness contract, the signature files would very quickly become
147 not just nullness annotations found in the source code and annotations merged
148 in from external sources, but also inferring whether nullness annotations have
165 nullness, such as attempting to change a nullness contract incompatibly
201 * Metalava can generate reports about nullness annotation coverage (which helps
222 324 methods and fields were missing nullness annotations out of 650 total
223 API references. API nullness coverage is 50%
430 For example, metalava has a feature to mark "newly annotated" nullness
[all …]
|
| D | FORMAT.md | 21 3. This is format v2, but with all nullness annotations replaced by a
34 developers), we'd like to have nullness annotations (as well as some other
58 but in v2 "String" means "String with unknown nullness".
72 @Override etc); only those which are significant for the API, such as nullness
100 explicit nullness, use Kotlin's syntax for nullness. That means that for
101 nullable elements, we add "?" after the type, for unknown nullness we add "!",
303 Note that this isn't just for Kotlin. Just like there are special nullness
430 the nullness as deprecation ones (which are specially supported in v3 via the
443 case of Kotlin code, a special JetBrains nullness annotation), or the one that
|
| D | USAGE.md | 22 - Rewriting of nullness annotations to @RecentlyNull/NonNull (`--migrate-nullness`,
|
| /tools/metalava/src/test/java/com/android/tools/metalava/ |
| D | NullnessMigrationTest.kt | 285 fun `Convert libcore nullness annotations to support`() { in Convert libcore nullness annotations to support()
442 fun `Migrate nullness for type-use annotations`() { in Migrate nullness for type-use annotations()
653 fun `Merge nullness annotations in stubs that are not in the API signature file`() { in Merge nullness annotations in stubs that are not in the API signature file()
|
| D | AndroidApiChecksTest.kt | 175 fun `Check Warnings for missing nullness annotations`() { in Check Warnings for missing nullness annotations()
|
| D | CompatibilityCheckTest.kt | 128 fun `Flag invalid nullness changes`() { in Flag invalid nullness changes()
2154 fun `Implicit nullness`() { in Implicit nullness()
|
| D | ApiLintTest.kt | 3860 fun `Nullability overrides in unbounded generics (one super method lacks nullness info)`() { in Nullability overrides in unbounded generics (one super method lacks nullness info)()
|
| D | ApiFileTest.kt | 820 fun `Known nullness`() { in Known nullness()
|
| /tools/metalava/src/main/java/com/android/tools/metalava/model/psi/ |
| D | PsiTypeItem.kt | 465 … val nullness = owner?.modifiers?.annotations()?.firstOrNull { it.isNullnessAnnotation() } in getCanonicalText() constant
466 var elementAnnotations = if (nullness != null) { listOf(nullness) } else null in getCanonicalText()
495 …} else if (nullness != null && owner.modifiers.isVarArg() && owner.isKotlin() && type is PsiEllips… in getCanonicalText()
498 val provider = if (nullness.isNonNull()) { in getCanonicalText()
|
| /tools/metalava/stub-annotations/ |
| D | README.md | 28 (5) We've tweaked the nullness annotations to include
|
| /tools/metalava/src/test/java/com/android/tools/metalava/model/psi/ |
| D | PsiTypePrinterTest.kt | 247 fun `Check other annotations than nullness annotations`() { in <lambda>()
|