Home
last modified time | relevance | path

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

/freebsd/include/
H A Dstdio.h139 int (* _Nullable _close)(void *); member
140 int (* _Nullable _read)(void *, char *, int); member
141 fpos_t (* _Nullable _seek)(void *, fpos_t, int); member
142 int (* _Nullable _write)(void *, const char *, int); member
427 int (* _Nullable)(void *, char *, int),
428 int (* _Nullable)(void *, const char *, int),
429 fpos_t (* _Nullable)(void *, fpos_t, int),
430 int (* _Nullable)(void *));
H A Dsignal.h117 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.h209 #define _Nullable macro
/freebsd/sys/sys/
H A Dcdefs.h527 #define _Nullable macro
/freebsd/contrib/llvm-project/clang/include/clang/Basic/
H A DAttrDocs.td4894 qualifiers indicate which pointer types can be null (``_Nullable``) or cannot
4898 type can be null (the ``_Nullable`` qualifier), doesn't have a defined meaning
4913 int fetch_or_zero(int * _Nullable ptr) {
4918 const char *join_strings(const char * _Nonnull * _Nullable strings, unsigned n);
4933 to C++ classes marked with the ``_Nullable`` attribute.
4940 ambiguous. For example, ``std::optional`` is not marked ``_Nullable``, because
4941 ``optional<int> _Nullable`` is redundant and ``optional<int> _Nonnull`` is
4971 The ``_Nullable`` nullability qualifier indicates that a value of the
4972 ``_Nullable`` pointer type can be null. For example, given:
4976 int fetch_or_zero(int * _Nullable ptr);
[all …]
H A DTokenKinds.def733 KEYWORD(_Nullable , KEYALL)
H A DAttr.td2565 let Spellings = [CustomKeyword<"_Nullable">];
H A DDiagnosticSemaKinds.td12558 "type specifier (_Nonnull, _Nullable, or _Null_unspecified)">,
12562 "_Nullable, or _Null_unspecified)">,
12565 "insert '%select{_Nonnull|_Nullable|_Null_unspecified}0' if the "