Lines Matching full:pointers

20 // expected nullability of pointers. These annotations allow you to designate
21 // pointers in one of three classification states:
23 //  * "Non-null" (for pointers annotated `Nonnull<T>`), indicating that it is
25 //  * "Nullable" (for pointers annotated `Nullable<T>`), indicating that it is
27 //  * "Unknown" (for pointers annotated `NullabilityUnknown<T>`), indicating
29 //    non-null. This is the default state of unannotated pointers.
31 // NOTE: unannotated pointers implicitly bear the annotation
55 // pointers to have more confidence in their null state. If a function declares
61 // of pointers, and these expectations are, in effect, a contract; often,
75 // consumers of these pointers across API boundaries to take appropriate steps
76 // when setting or using these pointers:
78 // * "Non-null" pointers should never be null. It is the responsibility of the
80 //   null. Consumers of such pointers can treat such pointers as non-null.
81 // * "Nullable" pointers may or may not be null. Consumers of such pointers
84 // * "Unknown" pointers may be either "non-null" or "nullable" but have not been
86 //   such pointers across API boundaries should determine --  over time -- to
88 //   pointers across an API boundary should continue to treat such pointers as
130 // pointers. User-defined types can indicate compatibility with nullability
193 // "non-null" or "nullable." Providers of such pointers across API boundaries
194 // should, over time, annotate such pointers as either "non-null" or "nullable."
195 // Consumers of these pointers across an API boundary should treat such pointers
196 // with the same caution they treat currently unannotated pointers. Most
197 // existing code will have "unknown"  pointers, which should eventually be
201 // NOTE: Because this annotation is the global default state, pointers without