| /third_party/rust/rust/tests/ui/or-patterns/ |
| D | remove-leading-vert.stderr | 45 | while parsing this or-pattern starting here
53 | while parsing this or-pattern starting here
61 | while parsing this or-pattern starting here
69 | while parsing this or-pattern starting here
77 | while parsing this or-pattern starting here
85 | while parsing this or-pattern starting here
93 | while parsing this or-pattern starting here
101 | while parsing this or-pattern starting here
109 | while parsing this or-pattern starting here
119 | while parsing this or-pattern starting here
[all …]
|
| D | multiple-pattern-typo.stderr | 7 | while parsing this or-pattern starting here
15 | while parsing this or-pattern starting here
23 | while parsing this or-pattern starting here
31 | while parsing this or-pattern starting here
39 | while parsing this or-pattern starting here
47 | while parsing this or-pattern starting here
|
| /third_party/skia/third_party/externals/angle2/src/gpu_info_util/ |
| D | SystemInfo_unittest.cpp | 18 // Test AMD Brahma driver version parsing
23 // Check parsing fails when no version string is present. in TEST()
27 // Check parsing when the string is just the version string, with and without dots in TEST()
33 // Check parsing with prefix / suffix in TEST()
42 // Test AMD Catalyst version parsing
47 // Check parsing fails when no version string is present. in TEST()
51 // Check parsing fails when ReleaseVersion= is present but no number appears in the line in TEST()
55 // Check parsing works on the simple case in TEST()
59 // Check parsing works if there are other lines in TEST()
63 // Check parsing get the first version string in TEST()
[all …]
|
| /third_party/json/tests/src/ |
| D | unit-class_parser.cpp | 362 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
364 …ion.parse_error.101] parse error at line 2, column 0: syntax error while parsing value - invalid s…
365 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
367 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
372 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
373 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
374 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
375 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
376 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
377 …ion.parse_error.101] parse error at line 1, column 2: syntax error while parsing value - invalid s…
[all …]
|
| /third_party/parse5/test/data/huge-page/ |
| D | huge-page.html | 361 …parsing>12.2 Parsing HTML documents</a><ol><li><a href=syntax.html#overview-of-the-parsing-model>1…
374 requirements given in the next section ("parsing HTML documents").</i></p>
1224 …parsing>12.2 Parsing HTML documents</h3><div class=status><input onclick=toggleStatus(this) value=…
1229 <p class=note>The rules for parsing XML documents into DOM trees are covered by the next
1230 …section, entitled "<a id=parsing:the-xhtml-syntax href=xhtml.html#the-xhtml-syntax>The XHTML synta…
1232 <p>User agents must use the parsing rules described in this section to generate the DOM trees from
1233 …<code id=parsing:text/html><a href=iana.html#text/html>text/html</a></code> resources. Together, t…
1239 XML, it is a separate language with its own parsing rules.</p>
1242 SGML parsing rules. However, few (if any) web browsers ever implemented true SGML parsing for
1254 <p>This specification defines the parsing rules for HTML documents, whether they are syntactically
[all …]
|
| /third_party/rust/crates/syn/src/ |
| D | attr.rs | 6 #[cfg(feature = "parsing")]
8 #[cfg(feature = "parsing")]
72 /// # Parsing from tokens to Attribute
113 /// # Parsing from Attribute to structured arguments
212 #[cfg(feature = "parsing")]
213 #[cfg_attr(doc_cfg, doc(cfg(feature = "parsing")))]
235 #[cfg(feature = "parsing")]
236 #[cfg_attr(doc_cfg, doc(cfg(feature = "parsing")))]
244 parsing::DisplayAttrStyle(&self.style), in parse_args_with()
245 parsing::DisplayPath(path), in parse_args_with()
[all …]
|
| D | token.rs | 32 //! # Parsing
78 //! - [Parsing] — `input.parse::<Token![...]>()?`
87 //! [Parsing]: crate::parse::ParseBuffer::parse()
91 #[cfg(feature = "parsing")]
94 #[cfg(feature = "parsing")]
96 #[cfg(feature = "parsing")]
98 #[cfg(feature = "parsing")]
100 #[cfg(feature = "parsing")]
102 #[cfg(feature = "parsing")]
104 #[cfg(feature = "parsing")]
[all …]
|
| D | discouraged.rs | 1 //! Extensions to the parsing API with niche applicability.
6 /// Extensions to the `ParseStream` API to support speculative parsing.
11 /// parse stream, perform some speculative parsing, then join the original
12 /// stream to the fork to "commit" the parsing from the fork to the main
20 /// an `A`, or that the `A`s are finished and it's time to start parsing
24 /// parsing `B*` and removing the leading members of `A` from the
26 /// speculative parsing.
35 /// 2544], [`PathSegment`] parsing should always try to consume a following
39 /// This is the exact kind of parsing behavior which requires the "fork,
107 /// The main drawback of this style of speculative parsing is in error
[all …]
|
| /third_party/mindspore/mindspore-src/source/mindspore/python/mindspore/rewrite/parsers/ |
| D | constant_parser.py | 36 stree ([SymbolTree]): Symbol Tree under parsing.
41 TypeError: Name parser only supports parsing ast.Name type nodes.
44 …raise TypeError(error_str(f"name parser only supports parsing ast.Name type nodes, but got ast typ…
61 stree ([SymbolTree]): Symbol Tree under parsing.
66 TypeError: Num parser only supports parsing ast.Num type nodes.
69 …raise TypeError(error_str(f"num parser only supports parsing ast.Num type nodes, but got ast type "
86 stree ([SymbolTree]): Symbol Tree under parsing.
94 TypeError:Str parser only supports parsing ast.Str type nodes.
97 …raise TypeError(error_str(f"str parser only supports parsing ast.Str type nodes, but got ast type "
|
| /third_party/rust/rust/tests/ui/parser/ |
| D | match-arm-without-braces.stderr | 7 | while parsing the `match` arm starting here
18 | -- while parsing the `match` arm starting here
33 | -- while parsing the `match` arm starting here
48 | -- while parsing the `match` arm starting here
69 | -- while parsing the `match` arm starting here
84 | -- while parsing the `match` arm starting here
99 | -- while parsing the `match` arm starting here
114 | -- while parsing the `match` arm starting here
122 | -- while parsing the `match` arm starting here
130 | -- while parsing the `match` arm starting here
|
| D | impl-parsing.stderr | 2 --> $DIR/impl-parsing.rs:4:11
8 --> $DIR/impl-parsing.rs:5:11
14 --> $DIR/impl-parsing.rs:6:6
20 --> $DIR/impl-parsing.rs:7:6
26 --> $DIR/impl-parsing.rs:9:1
34 --> $DIR/impl-parsing.rs:9:9
|
| D | nt-parsing-has-recovery.stderr | 2 --> $DIR/nt-parsing-has-recovery.rs:5:10
5 | ------- while parsing argument for this `expr` macro fragment
11 --> $DIR/nt-parsing-has-recovery.rs:6:10
14 | ------- while parsing argument for this `expr` macro fragment
20 --> $DIR/nt-parsing-has-recovery.rs:9:33
|
| /third_party/openhitls/tls/handshake/parse/src/ |
| D | parse_common.h | 40 * @param pkt [IN] Context for parsing
51 * @param pkt [IN] Context for parsing
64 * @param pkt [IN] Context for parsing
78 * @param pkt [IN] Context for parsing
111 * @param pkt [IN] Context for parsing
122 * @param pkt [IN] Context for parsing
133 * @param pkt [IN] Context for parsing
144 * @param pkt [IN] Context for parsing
155 * @param pkt [IN] Context for parsing
167 * @param pkt [IN] Context for parsing
[all …]
|
| /third_party/python/Doc/library/ |
| D | xml.sax.handler.rst | 33 This interface specifies only those DTD events required for basic parsing
66 | access: (parsing) read-only; (not parsing) read/write
76 | access: (parsing) read-only; (not parsing) read/write
85 | access: (parsing) read-only; (not parsing) read/write
94 | access: (parsing) read-only; (not parsing) read/write
102 | access: (parsing) read-only; (not parsing) read/write
112 | access: (parsing) read-only; (not parsing) read/write
142 | description: When parsing, the current DOM node being visited if this is
143 a DOM iterator; when not parsing, the root DOM node for iteration.
144 | access: (parsing) read-only; (not parsing) read/write
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/Remarks/ |
| D | BitstreamRemarkParser.cpp | 26 "Error while parsing %s: unknown record entry (%lu).", BlockName, in unknownRecord()
33 "Error while parsing %s: malformed record entry (%s).", BlockName, in malformedRecord()
167 "Error while parsing %s: expecting [ENTER_SUBBLOCK, %s, ...].", in parseBlock()
187 "Error while parsing %s: expecting records.", BlockName); in parseBlock()
198 "Error while parsing %s: unterminated block.", BlockName); in parseBlock()
230 "Error while parsing BLOCKINFO_BLOCK: expecting [ENTER_SUBBLOCK, " in parseBlockInfoBlock()
241 "Error while parsing BLOCKINFO_BLOCK."); in parseBlockInfoBlock()
263 "Unexpected error while parsing bitstream."); in isBlock()
375 "Error while parsing BLOCK_META: missing container version."); in processCommonMeta()
382 "Error while parsing BLOCK_META: invalid container type."); in processCommonMeta()
[all …]
|
| /third_party/icu/docs/userguide/format_parse/ |
| D | index.md | 12 # Formatting and Parsing
38 and parsing and allow the separation of the data that the end-user sees from the
41 other object from its internal representation into a string. Parsing is the
71 > :point_right: **Note**: Although parsing is supported in several legacy ICU APIs,
147 ## Formatting and Parsing Classes
157 for formatting and parsing numbers, dates, strings and other objects.
166 A concrete class for holding the parse position in a string during parsing.
178 `UParseError` is used to returned detailed information about parsing errors.
179 It is used by the ICU parsing engines that parse long rules, patterns, or
189 parsing localized strings to `Number` objects.
[all …]
|
| /third_party/python/Lib/xml/sax/ |
| D | handler.py | 92 not invoke this method until it has either abandoned parsing
174 if they are capable of parsing and using content models.
212 parsing (unparsed entities and attributes)."""
247 # access: (parsing) read-only; (not parsing) read/write
254 # access: (parsing) read-only; (not parsing) read/write
260 # access: (parsing) read-only; (not parsing) read/write
266 # access: (parsing) read-only; (not parsing) read/write
271 # access: (parsing) read-only; (not parsing) read/write
278 # access: (parsing) read-only; (not parsing) read/write
307 # description: When parsing, the current DOM node being visited if this is
[all …]
|
| /third_party/rust/rust/tests/ui/did_you_mean/ |
| D | issue-40006.stderr | 5 | - while parsing this item list starting here
18 | - while parsing this item list starting here
29 | - while parsing this item list starting here
45 | - while parsing this item list starting here
55 | - while parsing this item list starting here
65 | - while parsing this item list starting here
75 | - while parsing this item list starting here
|
| /third_party/json/docs/mkdocs/docs/api/basic_json/ |
| D | is_discarded.md | 9 - the value was discarded during parsing with a callback function (see [`parser_callback_t`](parser…
10 - the value is the result of parsing invalid JSON with parameter `allow_exceptions` set to `#!cpp f…
44 !!! note "Removal during parsing with callback functions"
46 … discarded by a callback function (see [`parser_callback_t`](parser_callback_t.md)) during parsing,
51 This function will always be `#!cpp false` for JSON values after parsing. That is, discarded values…
52 during parsing, but will be removed when inside a structured value or replaced by null in other cas…
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/include/llvm/AsmParser/ |
| D | Parser.h | 32 /// run the verifier after parsing the file to check that it is okay.
38 /// parsing.
52 /// run the verifier after parsing the file to check that it is okay.
58 /// parsing.
82 /// run the verifier after parsing the file to check that they are okay.
88 /// parsing.
103 /// should run the verifier after parsing the file to check that it is okay.
115 /// parsing.
131 /// parsing.
164 /// parsing.
[all …]
|
| /third_party/skia/m133/third_party/externals/expat/expat/tests/ |
| D | nsalloc_tests.c | 75 /* Test the effects of allocation failure in simple namespace parsing.
101 fail("Parsing worked despite failing allocations"); in START_TEST()
103 fail("Parsing failed even at maximum allocation count"); in START_TEST()
245 fail("Parsing worked despite failing allocations"); in START_TEST()
247 fail("Parsing failed even at max allocation count"); in START_TEST()
305 fail("Parsing worked despite failing allocations"); in START_TEST()
307 fail("Parsing failed even at max allocation count"); in START_TEST()
348 fail("Parsing worked despite failing allocations"); in START_TEST()
350 fail("Parsing failed even at max allocation count"); in START_TEST()
434 fail("Parsing worked despite failing allocations"); in START_TEST()
[all …]
|
| /third_party/popt/ |
| D | popt.3 | 48 The popt library exists essentially for parsing command-line
50 parsing the argv array by hand or using the getopt functions
57 .RI "variables, thus enabling multiple passes in parsing " argv
59 allowing parsing of command-line-strings from any source;
179 the parsing function not to return a value, since the value of \fIval\fP
188 .RI "The next option, " val ", is the value popt's parsing function
189 should return when the option is encountered. If it is 0, the parsing
190 function does not return a value, instead parsing the next
242 a table, the parsing function never returns information on an option in
267 popt can interleave the parsing of multiple command-line sets. It allows
[all …]
|
| /third_party/rust/rust/tests/ui/editions/ |
| D | edition-keywords-2018-2015-parsing.stderr | 2 --> $DIR/edition-keywords-2018-2015-parsing.rs:16:13
13 --> $DIR/edition-keywords-2018-2015-parsing.rs:26:13
24 --> $DIR/edition-keywords-2018-2015-parsing.rs:20:31
36 --> $DIR/edition-keywords-2018-2015-parsing.rs:21:35
53 ::: $DIR/edition-keywords-2018-2015-parsing.rs:24:8
59 --> $DIR/edition-keywords-2018-2015-parsing.rs:29:33
|
| D | edition-keywords-2018-2018-parsing.stderr | 2 --> $DIR/edition-keywords-2018-2018-parsing.rs:16:13
13 --> $DIR/edition-keywords-2018-2018-parsing.rs:26:13
24 --> $DIR/edition-keywords-2018-2018-parsing.rs:20:31
36 --> $DIR/edition-keywords-2018-2018-parsing.rs:21:35
53 ::: $DIR/edition-keywords-2018-2018-parsing.rs:24:8
59 --> $DIR/edition-keywords-2018-2018-parsing.rs:29:33
|
| /third_party/python/Lib/email/ |
| D | errors.py | 13 """Base class for message parsing errors."""
17 """Error while parsing headers."""
32 # These are parsing defects which the parser was able to work around.
79 # These errors are specific to header parsing.
109 # This defect only occurs during unicode parsing, not when
110 # parsing messages decoded from binary.
|