255960dd37
Type names ending in 'List' can clash with qapi list types in
generated C. We don't currently use such names. It is easier to
outlaw them now than to worry about how to resolve such a clash
in the future. For precedence, see commit 4dc2e69, which did the
same for names ending in 'Kind' versus implicit enum types for
qapi unions.
Update the testsuite to match.
Signed-off-by: Eric Blake <eblake@redhat.com>
Message-Id: <1445898903-12082-5-git-send-email-eblake@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
6 lines
241 B
JSON
6 lines
241 B
JSON
# Potential C name collision
|
|
# We reserve names ending in 'List' for use by array types.
|
|
# TODO - we could choose array names to avoid collision with user types,
|
|
# in order to let this compile
|
|
{ 'struct': 'FooList', 'data': { 's': 'str' } }
|