Home
last modified time | relevance | path

Searched refs:potential (Results 1 – 25 of 674) sorted by relevance

12345678910>>...27

/third_party/rust/crates/clap/src/parser/
Dvalidator.rs464 potential: FlatMap<Id, Vec<Id>>, field
469 let mut potential = FlatMap::new(); in with_args() localVariable
470 potential.extend_unchecked( in with_args()
479 Self { potential } in with_args()
494 for (other_arg_id, other_arg_id_conflicts) in self.potential.iter() { in gather_conflicts()
512 self.potential.get(arg_id).map(Vec::as_slice) in get_direct_conflicts()
/third_party/vk-gl-cts/external/vulkan-docs/src/proposals/
DVK_EXT_swapchain_maintenance1.adoc91 A potential library with a swapchain implementation can be conceived which
102 There are three potential solutions for this:
123 Regarding image count, potential solutions are:
125 * Specify all potential present modes at swapchain creation time
134 supports, potential solutions are:
148 potential set of present modes at swapchain creation time.
234 During creation of the swapchain, all potential present modes are specified by
/third_party/python/Misc/NEWS.d/
D3.5.5rc1.rst10 considered a potential security issue, as it may lead to privileged
47 Fix potential crash during GC caused by ``tp_dealloc`` which doesn't call
/third_party/libffi/src/alpha/
Dosf.S71 # Load up all of the (potential) argument registers.
177 # Store all of the potential argument registers in va_list format.
/third_party/skia/specs/
DREADME.md4 This folder contains potential new specs for platforms such as the web.
/third_party/flutter/skia/specs/
DREADME.md4 This folder contains potential new specs for platforms such as the web.
/third_party/skia/tests/sksl/runtime_errors/
DIllegalRecursionSimple.skvm3 error: 4: potential recursion (function call cycle) not allowed:
DIllegalRecursionMutual.skvm3 error: 5: potential recursion (function call cycle) not allowed:
DIllegalRecursionComplex.skvm3 error: 16: potential recursion (function call cycle) not allowed:
/third_party/openssl/doc/man3/
DOSSL_DECODER_from_bio.pod64 /* error: no suitable potential decoders found */
92 /* error: no suitable potential decoders found */
DOSSL_ENCODER_to_bio.pod73 /* error: no suitable potential encoders found */
100 /* error: no suitable potential encoders found */
/third_party/python/Misc/NEWS.d/next/Security/
D2022-11-04-09-29-36.gh-issue-98433.l76c5G.rst3 This prevents a potential CPU denial of service if an out-of-spec excessive
D2022-09-07-10-42-00.gh-issue-97514.Yggdsl.rst10 This was a potential privilege escalation. Filesystem based socket permissions
/third_party/skia/third_party/externals/libpng/contrib/pngminus/
DCHANGES.txt8 1.3 - 2017.08.24 - Fix potential overflow in buffer-size check
/third_party/flutter/skia/third_party/externals/libpng/contrib/pngminus/
DCHANGES.txt8 1.3 - 2017.08.24 - Fix potential overflow in buffer-size check
/third_party/cJSON/
DCHANGELOG.md5 * Fix potential core dumped for strrchr, see [#546](https://github.com/DaveGamble/cJSON/pull/546)
41 * Fix infinite loop in `cJSON_Minify` (potential Denial of Service). Thanks @Alanscut for reporting…
100 * Fix potential use after free if the `string` parameter to `cJSON_AddItemToObject` is an alias of …
106 * Fix potential double free, thanks @projectgus for reporting [#241](https://github.com/DaveGamble/…
266 * Fix a potential null pointer dereference in cJSON_Utils, see [795c3ac](https://github.com/DaveGam…
353 * runtime checks for a lot of potential integer overflows
355 * fix several potential issues found by [Coverity](https://scan.coverity.com/projects/cjson)
393 * Fixes a potential null pointer dereference in cJSON_Utils, discovered using clang's static analyz…
/third_party/typescript/tests/baselines/reference/
DinvalidTryStatements.types8 finally { } // potential error; can be absorbed by the 'catch'
DunderscoreThisInDerivedClass01.types10 // for capturing any potential return values from super calls,
DinvalidTryStatements.symbols8 finally { } // potential error; can be absorbed by the 'catch'
DunderscoreThisInDerivedClass01.symbols10 // for capturing any potential return values from super calls,
/third_party/rust/crates/tracing/.github/ISSUE_TEMPLATE/
Dfeature_request.md33 their potential drawbacks? Why was the proposed solution chosen over these
/third_party/mesa3d/docs/relnotes/
D6.5.1.rst74 - fixed potential dangling pointer bug in glBindProgram()
75 - fixed some memory leaks (and potential crashes) in Xlib driver
/third_party/cups-filters/m4/
Dac_ln_srf.m441 # your modified version has the potential to copy into its output some
45 # such potential, you must delete any notice of this special exception
/third_party/skia/third_party/externals/spirv-cross/shaders/frag/
Dfor-loop-init.frag17 // A potential loop variables, but we access it outside the loop,
/third_party/skia/third_party/externals/spirv-cross/shaders-msl/frag/
Dfor-loop-init.frag17 // A potential loop variables, but we access it outside the loop,

12345678910>>...27