/third_party/parse5/scripts/generate-named-entity-data/ |
D | README.md | 5 in tokenizer. This approach suffered from huge constant memory consumption: the in-memory size of t… 6 This new approach reduces the size of the character reference data to ~250Kb and maintains performa… 44 This approach has two advantages: 66 approach is to use, e.g. `0` as the node marker, followed by number of data bytes, followed by data… 90 to previous approach where branch lookup was implemented as dictionary lookup which is `O(1)`. Howe…
|
/third_party/boost/libs/asio/doc/overview/ |
D | threads.qbk | 20 which completion handlers may be invoked. This approach may also be used with 38 This approach is complemented by the following guarantee: 46 The reasons for this approach include:
|
D | async.qbk | 13 disadvantages of this approach, when compared to a synchronous-only or Reactor 14 approach, are outlined below. 68 approach corresponds to the Proactor design pattern as follows: 90 implementation approach corresponds to the Proactor design pattern as follows: 128 synchronous-only approach would require) can degrade system performance, due to
|
/third_party/flatbuffers/docs/source/ |
D | CUsage.md | 78 the top-down approach. 83 The tutorial uses a bottom up approach. In C it is also possible to use 84 a top-down approach by starting and ending objects nested within each 171 The `FLATBUFFERS_WRAP_NAMESPACE` approach used in the tutorial is convenient 173 the best approach. If the namespace is absent, or simple and 176 mentioned above uses this approach.
|
/third_party/boost/libs/endian/doc/endian/ |
D | choosing_approach.adoc | 12 NOTE: Deciding which is the best endianness approach (conversion functions, buffer 19 The best approach to endianness for a particular application depends on the 133 not a concern since this approach uses ordinary {cpp} arithmetic types to hold 137 approach avoids unnecessary conversions, it can result in the introduction of 273 The <<arithmetic,endian arithmetic approach>> is recommended to meet these 287 These factors all argue for an <<conversion, endian conversion approach>> that 301 The <<buffers,endian buffers>> approach is made-to-order for this use case. 314 <<arithmetic,endian arithmetic approach>>.
|
D | overview.adoc | 18 successful use, and each approach has use cases where it is preferred over the 85 Each approach has a long history of successful use, and each approach has use 143 |Endian arithmetic type approach |Endian conversion function approach 184 |Endian arithmetic type approach |Endian conversion function approach 217 With the Endian arithmetic approach, on little endian platforms an implicit 219 Endian conversion function approach, the user has ensured the conversions are
|
/third_party/skia/third_party/externals/opengl-registry/extensions/INTEL/ |
D | INTEL_framebuffer_CMAA.txt | 56 Conservative Morphological Anti-Aliasing (CMAA) is an alternative approach 103 dimensions/internal formats, what is the best approach in terms of 114 Whilst both approaches are functionally correct, approach b is more
|
/third_party/openGLES/extensions/INTEL/ |
D | INTEL_framebuffer_CMAA.txt | 56 Conservative Morphological Anti-Aliasing (CMAA) is an alternative approach 103 dimensions/internal formats, what is the best approach in terms of 114 Whilst both approaches are functionally correct, approach b is more
|
/third_party/node/deps/npm/node_modules/graceful-fs/ |
D | README.md | 63 builtin, and the approach by which a non-monkey-patched `fs` was 70 There are advantages to each approach. Monkey-patching the fs means 80 The current approach loads the `fs` module, and then creates a 93 * Monkey-patch fs, because the eval approach no longer works on recent
|
/third_party/boost/libs/mp11/doc/mp11/ |
D | overview.adoc | 15 approach outlined in the article 28 Another distinguishing feature of this approach is that lists (`L<T...>`) have the same form as
|
/third_party/mbedtls/docs/architecture/testing/ |
D | psa-storage-format-testing.md | 11 ## General approach 13 ### Limitations of a direct approach argument 19 An alternative, semi-direct approach consists of generating test data under version V, and reading … 21 ### Save-and-compare approach argument 27 …own to be identical to the state that V would have produced. Thus, this approach validates that W … 31 Use a similar approach for files other than keys where possible and relevant.
|
/third_party/boost/libs/spirit/doc/x3/tutorial/ |
D | tutorial_intro.qbk | 15 significantly reduces development time. Programmers typically approach parsing 37 We will present the tutorials in a cookbook style approach. This style of
|
/third_party/boost/libs/spirit/doc/qi/ |
D | tutorial_intro.qbk | 15 significantly reduces development time. Programmers typically approach parsing 37 We will present the tutorials in a cookbook style approach. This style of
|
/third_party/googletest/googletest/ |
D | README.md | 66 And a more robust and flexible approach is to build GoogleTest as part of that 76 location. This is the least flexible approach and can make it more difficult 79 source tree. This is often the simplest approach, but is also the hardest to 85 approach doesn't have the limitations of the other methods. 109 Note that this approach requires CMake 3.14 or later due to its use of the
|
/third_party/curl/docs/cmdline-opts/ |
D | proxytunnel.d | 8 the proxy. The tunnel approach is made with the HTTP proxy CONNECT request and
|
/third_party/skia/third_party/externals/angle2/src/libANGLE/renderer/metal/doc/ |
D | TransformFeedback.md | 52 - Instead of executing the same Vertex Shader's logic twice, one alternative approach is writing the 60 - However, this approach might even be slower than executing the Vertex Shader twice. Because a 65 enabled, the original approach will just simply executes the Vertex Shader once and use a cheap
|
/third_party/boost/libs/program_options/doc/ |
D | program_options.dox | 75 - @ref multiple_modules "possible approach for multi-module programs" 89 - @ref multiple_modules "possible approach for multi-module programs" 140 some options. One possible approach is show here.
|
/third_party/flutter/skia/third_party/externals/sdl/docs/ |
D | README-cmake.md | 6 approach has suffered from several issues across the different supported
|
/third_party/boost/libs/iterator/doc/ |
D | iterator_facade_body.rst | 30 policy objects to specify the behavior, but that approach was 34 overhead that can be avoided with the current approach. 36 2. The policy object approach does not allow for custom constructors 162 implemented as a proxy containing a copy of ``p+n``). This approach
|
/third_party/boost/libs/mp11/ |
D | README.md | 4 It implements the approach outlined in the article
|
/third_party/boost/libs/outcome/doc/src/content/tutorial/advanced/constructors/ |
D | metaprogrammg1.md | 26 approach than alternatives. We shall briefly cover those at the end of this section.
|
/third_party/boost/libs/outcome/doc/src/content/tutorial/advanced/interop/ |
D | conclusion.md | 12 better, and certainly simpler, approach.
|
/third_party/skia/third_party/externals/opengl-registry/extensions/EXT/ |
D | EXT_blend_equation_separate.txt | 75 This is different from the ATI_blend_equation_separate approach 275 This is a different approach than taken by the EXT_blend_func_separate 276 extension, but matches the approach taken by other "split" OpenGL 292 The point size ranges approach is preferable because it minimizes
|
/third_party/openGLES/extensions/EXT/ |
D | EXT_blend_equation_separate.txt | 75 This is different from the ATI_blend_equation_separate approach 275 This is a different approach than taken by the EXT_blend_func_separate 276 extension, but matches the approach taken by other "split" OpenGL 292 The point size ranges approach is preferable because it minimizes
|
/third_party/skia/third_party/externals/opengl-registry/extensions/OES/ |
D | OES_depth_texture.txt | 55 Resolution: Adopt approach b). Manual generation of mipmaps is done by averaging a 57 sense for depth textures. A better approach would be to take a min or max of 2 x 2 texel 72 Resolution: Adopt approach b). We only need to support one way of treating how depth textures
|