Home
last modified time | relevance | path

Searched refs:_Nullable (Results 1 – 9 of 9) sorted by relevance

/freebsd/include/
H A Dstdio.h135 int (* _Nullable _close)(void *); member
136 int (* _Nullable _read)(void *, char *, int); member
137 fpos_t (* _Nullable _seek)(void *, fpos_t, int); member
138 int (* _Nullable _write)(void *, const char *, int); member
418 int (* _Nullable)(void *, char *, int),
419 int (* _Nullable)(void *, const char *, int),
420 fpos_t (* _Nullable)(void *, fpos_t, int),
421 int (* _Nullable)(void *));
H A Dsignal.h109 void (* _Nullable sigset(int, void (* _Nullable)(int)))(int); variable
H A Derr.h62 void err_set_exit(void (* _Nullable)(int));
/freebsd/tools/build/cross-build/include/common/sys/
H A Dcdefs.h201 #define _Nullable macro
/freebsd/sys/sys/
H A Dcdefs.h661 #define _Nullable macro
/freebsd/contrib/llvm-project/clang/include/clang/Basic/
H A DAttrDocs.td4141 qualifiers indicate which pointer types can be null (``_Nullable``) or cannot
4145 type can be null (the ``_Nullable`` qualifier), doesn't have a defined meaning
4160 int fetch_or_zero(int * _Nullable ptr) {
4165 const char *join_strings(const char * _Nonnull * _Nullable strings, unsigned n);
4180 to C++ classes marked with the ``_Nullable`` attribute.
4187 ambiguous. For example, ``std::optional`` is not marked ``_Nullable``, because
4188 ``optional<int> _Nullable`` is redundant and ``optional<int> _Nonnull`` is
4218 The ``_Nullable`` nullability qualifier indicates that a value of the
4219 ``_Nullable`` pointer type can be null. For example, given:
4223 int fetch_or_zero(int * _Nullable ptr);
[all …]
H A DTokenKinds.def718 KEYWORD(_Nullable , KEYALL)
H A DAttr.td2273 let Spellings = [CustomKeyword<"_Nullable">];
H A DDiagnosticSemaKinds.td11942 "type specifier (_Nonnull, _Nullable, or _Null_unspecified)">,
11946 "_Nullable, or _Null_unspecified)">,
11949 "insert '%select{_Nonnull|_Nullable|_Null_unspecified}0' if the "