Lines Matching full:submessage
173 "only length-delimited submessage fields may be lazy");
264 /* All submessage fields are lower than all other fields.
1267 upb_status_seterrmsg(s, "invalid subdef type for this submessage field");
2185 /* For each submessage field, get or create a handlers object and set it as
2214 * subhandlers for this submessage field. */
2217 /* The selector for a submessage field is the field index. */
2354 /* The effective type of the submessage; not used yet.
2355 * if (type == SUBMESSAGE &&
2595 * cases (submessage has handlers or not) as opposed to three
2596 * (submessage has handlers in enclosing message but no subhandlers).
2599 * notice a submessage but skip its contents (like if we're testing
2600 * for submessage presence or counting the number of repeated
2601 * submessages). In this case we will end up parsing the submessage
2606 * submessage but no subhandlers. The uses cases for this are
2613 /* TODO(haberman): check type of submessage.
3828 * (ie. submessage types). Adds duplicates of existing defs to addtab
7796 /* Generates bytecode to parse a single string or lazy submessage field. */
8166 "Submessage end extends past enclosing submessage.";
8333 seterr(d, "Skipped value extended beyond enclosing submessage.");
8496 seterr(d, "Submessage ended in the middle of a value or group");
8651 * field number) prior to hitting any enclosing submessage end, pushing our
9101 seterr(d, "Unexpected EOF inside submessage or group");
9229 ** 1. buffer all submessage data in a temporary buffer, then copy it exactly
9237 ** ahead-of-time for each submessage length. If we overallocated, we waste
9266 ** and lengths. When the top-level submessage ends, we can go beginning to end,
9279 * occur at a single submessage level. Every segment contains one or more runs.
9283 * .--Submessage lengths---------.
9298 * observe how the second segment spans both the inner submessage and part of
9329 * segment where this submessage's length is being accumulated. */
10335 * begin a sequence of mapentry messages rather than a single submessage. */
10340 * (subobjects, strings, numbers, and bools) that the map-entry submessage
11191 /* Helper: emit one map entry (as a submessage in the map field sequence). This
11194 * buffer, emits the handler calls to start the mapentry submessage (setting up
12028 * message->repeated field->submessage->repeated field->... nesting. */
12574 /* Set up handlers for a mapentry submessage (i.e., an individual key/value pair
12579 * temporary structure at the start of a mapentry submessage, store key and
12581 * key/value pair once at the end of the submessage. If we don't do this, we
