Lines Matching refs:mapentry
236 /* Ensure that MapEntry submessages only appear as repeated fields, not
243 "Field %s refers to mapentry message but is not "
6999 static bool msg_onmapentry(void *closure, const void *hd, bool mapentry) {
7004 upb_msgdef_setmapentry(m, mapentry);
10335 * begin a sequence of mapentry messages rather than a single submessage. */
11124 /* Helper: invoked during parse_mapentry() to emit the mapentry message's key
11139 upb_status_seterrmsg(&p->status, "mapentry message has no key");
11194 * buffer, emits the handler calls to start the mapentry submessage (setting up
11196 * value parser (invoked next) will emit the mapentry's value field and then
11197 * end the mapentry message. */
11206 * for the mapentry itself, and then set |f| in that frame so that the map
11240 upb_status_seterrmsg(&p->status, "mapentry message has no value");
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
12583 * our sources that emit mapentry messages do so canonically (with one key
12590 /* A mapentry message is printed simply as '"key": value'. Rather than
12684 /* mapentry messages are sufficiently different that we handle them
