Searched refs:these (Results 1 – 25 of 5719) sorted by relevance
12345678910>>...229
/third_party/typescript/tests/baselines/reference/ |
D | objectTypeHidingMembersOfObjectAssignmentCompat2.errors.txt | 2 The types returned by 'toString()' are incompatible between these types. 5 The types returned by 'toString()' are incompatible between these types. 8 The types returned by 'toString()' are incompatible between these types. 11 The types returned by 'toString()' are incompatible between these types. 14 The types returned by 'toString()' are incompatible between these types. 28 !!! error TS2322: The types returned by 'toString()' are incompatible between these types. 33 !!! error TS2696: The types returned by 'toString()' are incompatible between these types. 43 !!! error TS2322: The types returned by 'toString()' are incompatible between these types. 48 !!! error TS2696: The types returned by 'toString()' are incompatible between these types. 57 !!! error TS2322: The types returned by 'toString()' are incompatible between these types.
|
D | objectTypeHidingMembersOfObjectAssignmentCompat.errors.txt | 2 The types returned by 'toString()' are incompatible between these types. 5 The types returned by 'toString()' are incompatible between these types. 8 The types returned by 'toString()' are incompatible between these types. 22 !!! error TS2322: The types returned by 'toString()' are incompatible between these types. 33 !!! error TS2322: The types returned by 'toString()' are incompatible between these types. 43 !!! error TS2322: The types returned by 'toString()' are incompatible between these types.
|
D | interfaceWithMultipleBaseTypes.errors.txt | 2 The types of 'x.b' are incompatible between these types. 7 The types of 'x.a' are incompatible between these types. 10 The types of 'x.b' are incompatible between these types. 44 !!! error TS2430: The types of 'x.b' are incompatible between these types. 84 !!! error TS2430: The types of 'x.a' are incompatible between these types. 88 !!! error TS2430: The types of 'x.b' are incompatible between these types.
|
D | deeplyNestedAssignabilityErrorsCombined.errors.txt | 2 The types of 'a.b.c.d.e.f().g' are incompatible between these types. 5 The types of '(new a.b.c.d.e.f()).g' are incompatible between these types. 15 !!! error TS2322: The types of 'a.b.c.d.e.f().g' are incompatible between these types. 31 !!! error TS2322: The types of '(new a.b.c.d.e.f()).g' are incompatible between these types.
|
D | callSignatureAssignabilityInInheritance.errors.txt | 2 The types returned by 'a(...)' are incompatible between these types. 5 The types returned by 'a2(...)' are incompatible between these types. 70 !!! error TS2430: The types returned by 'a(...)' are incompatible between these types. 80 !!! error TS2430: The types returned by 'a2(...)' are incompatible between these types.
|
/third_party/skia/third_party/externals/libwebp/ |
D | PATENTS | 10 run, modify and propagate the contents of these implementations of WebM, where 13 infringed by these implementations of WebM. This grant does not include claims 14 that would be infringed only as a consequence of further modification of these 18 counterclaim in a lawsuit) alleging that any of these implementations of WebM 19 or any code incorporated within any of these implementations of WebM 22 for these implementations of WebM shall terminate as of the date such
|
/third_party/flutter/skia/third_party/externals/libwebp/ |
D | PATENTS | 10 run, modify and propagate the contents of these implementations of WebM, where 13 infringed by these implementations of WebM. This grant does not include claims 14 that would be infringed only as a consequence of further modification of these 18 counterclaim in a lawsuit) alleging that any of these implementations of WebM 19 or any code incorporated within any of these implementations of WebM 22 for these implementations of WebM shall terminate as of the date such
|
/third_party/boost/libs/asio/doc/requirements/ |
D | asynchronous_socket_operations.qbk | 24 then the `buffers` are filled in the order in which these operations were 25 issued. The order of invocation of the completion handlers for these operations 32 order in which these operations were issued. 36 are transmitted in the order in which these operations were issued. The order 37 of invocation of the completion handlers for these operations is unspecified.
|
/third_party/gstreamer/gstreamer/docs/random/ |
D | streamheader | 2 data stream. With these initial buffers, it can pick up at any point in 11 receive these initial buffers. Also, sink elements should know that these 13 for example, multifdsink needs to send these initial buffers before the 24 It is of course important that these streamheader buffers are not sent twice 38 - each of these buffers should then have these caps set on them. 79 aware of a HEADER flag, causing them to keep these buffers around and push 84 these header buffers. But similarly,
|
/third_party/boost/libs/thread/doc/ |
D | configuration.qbk | 98 When `BOOST_THREAD_PROVIDES_THREAD_EQ` is defined Boost.Thread provides these deprecated feature. 141 When `BOOST_THREAD_PROVIDES_NESTED_LOCKS` is defined Boost.Thread provides these deprecated feature… 158 When `BOOST_THREAD_VERSION>=4` define `BOOST_THREAD_PROVIDES_NESTED_LOCKS` if you want these featur… 167 Define `BOOST_THREAD_DONT_PROVIDE_BASIC_THREAD_ID ` if you don't want these features. 172 … one that is used for PTheads based platforms. In order to have access to these functions, the use… 174 …VERSION==2` define `BOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN ` if you want these features. 175 …` define `BOOST_THREAD_DONT_PROVIDE_GENERIC_SHARED_MUTEX_ON_WIN ` if you don't want these features. 182 …xplicitly `BOOST_THREAD_PROVIDES_SHARED_MUTEX_UPWARDS_CONVERSIONS` to get these upwards conversion… 184 …ON==2` define `BOOST_THREAD_PROVIDES_SHARED_MUTEX_UPWARDS_CONVERSIONS ` if you want these features. 185 …fine `BOOST_THREAD_DONT_PROVIDE_SHARED_MUTEX_UPWARDS_CONVERSION ` if you don't want these features. [all …]
|
/third_party/flutter/flutter/ |
D | .gitattributes | 4 # Always perform LF normalization on these files 17 # Make sure that these Windows files always have CRLF line endings in checkout 21 # Never perform LF normalization on these files
|
/third_party/boost/libs/math/doc/sf/ |
D | zeta.qbk | 19 The return type of these functions is computed using the __arg_promotion_rules: 62 The tests for these functions come in two parts: 68 versions of these functions use differing implementations internally, so this 74 All versions of these functions first use the usual reflection formulas 79 The generic versions of these functions are implemented using the series: 117 and for positive odd integers we simply cache pre-computed values as these are of great
|
/third_party/openssl/doc/man3/ |
D | OPENSSL_fork_prepare.pod | 26 Platforms without fork(2) will probably not need to use these functions. 29 such as Linux that have both functions will normally not need to call these 32 L<OPENSSL_init_crypto(3)> will register these functions with the appropriate 34 applications, these functions can be called directly. They should be used
|
/third_party/ltp/testcases/open_posix_testsuite/conformance/interfaces/clock_gettime/ |
D | rationale.txt | 1 For these tests, the date returned by clock_gettime() will be compared 5 - Machines running these test cases also have access to the gettimeofday 14 It turns out these two functions _should_ return the same value but do
|
/third_party/boost/libs/math/doc/fp_utilities/ |
D | fpclassify.qbk | 28 to use these functions. 33 name in C99, indeed if the C99 macros are available, then these functions 37 Note that the definition of these functions 38 ['does not suppress the definition of these names as macros by math.h] 40 these as macros. That mean that the following have differing meanings: 70 Detailed descriptions for each of these functions follows:
|
/third_party/ltp/testcases/kernel/device-drivers/ |
D | README | 4 these test will manipulate devices and may leave them in an unstable state, 5 these tests should not be run when other important system tasks are being 9 To build and execute these tests:
|
/third_party/cef/tools/distrib/linux/ |
D | README.redistrib.txt | 36 be used. Without these files arbitrary Web components may display 48 Without these files arbitrary Web components may display incorrectly. 54 Without these files the aforementioned capabilities may fail. 62 these files the aforementioned capabilities may fail when GPU acceleration is
|
/third_party/gstreamer/gstplugins_base/gst-libs/gst/gl/glprototypes/ |
D | README | 29 * definitions for these macros. The macros are given the following arguments: 35 * @min_gl_major: the major part of the minimum GL version where these 38 * @min_gl_minor: the minor part of the minimum GL version where these 52 * @extension_names: A list of extension names to try. If any of these
|
/third_party/node/deps/npm/node_modules/wcwidth/docs/ |
D | index.md | 25 In all these cases, there is no ambiguity about which width a 29 Choosing single-width for these characters is easy to justify as 31 displaying these characters as double-width comes from historic 38 of these characters. It would nevertheless make sense 51 but also of each presentation form, something the author of these
|
/third_party/boost/libs/vmd/doc/ |
D | vmd_naming.qbk | 24 I have used most of these names in order to mimic the naming of Boost PP 26 'seq', and 'tuple' refer to these Boost PP data types unless otherwise 27 noted. See the help for Boost PP for any explanation of these 47 and the term 'identifier' refers to a VMD identifier. All these will be explained
|
/third_party/cef/tools/distrib/win/ |
D | README.redistrib.txt | 37 configured the default locale of "en-US" will be used. Without these files 49 Without these files arbitrary Web components may display incorrectly. 63 Without these files the aforementioned capabilities may fail. 71 these files the aforementioned capabilities may fail when GPU acceleration is
|
/third_party/boost/libs/outcome/doc/src/content/tutorial/essential/coroutines/ |
D | awaitables.md | 10 `BOOST_OUTCOME_V2_NAMESPACE::experimental::awaitables`) these awaitable types suitable 16 of these immediately begins the execution of the function now. If the function never 22 literature): invoking `co_await` upon a function returning one of these causes the
|
/third_party/node/deps/npm/ |
D | .npmignore | 16 # don't need these in the npm package. 20 # these are used in some tests.
|
/third_party/boost/libs/config/doc/ |
D | cstdint.qbk | 20 The specifications for these types are based on the ISO/IEC 9899:1999 C Language standard header <s… 37 Because these are boost headers, their names conform to boost header naming conventions rather than 45 visible to users of <boost/cstdint.hpp>. Don't use these macros; they are not part of 49 in the global namespace to users of <boost/cstdint.hpp>. Don't use these names, they are not part of 101 There is no guarantee that these types are fastest for all purposes. In any case, however, they sat… 134 The following macros are always defined after inclusion of this header, these allow 153 …apable of storing a pointer. The macro [^BOOST_HAS_INTPTR_T] is set when these types are availabl…
|
/third_party/boost/libs/math/doc/complex/ |
D | complex-tr1.qbk | 10 present in the C++ standard. Equivalents to these functions are part of the C99 standard, and 15 Although there are deceptively simple formulae available for all of these functions, a naive 16 implementation that used these formulae would fail catastrophically for some input 17 values. The Boost versions of these functions have been implemented using the methodology 23 actually a representable value. The maximum theoretical relative error for all of these functions
|
12345678910>>...229