• E
    qapi: Check for member name conflicts with a base class · ff55d72e
    Eric Blake 提交于
    Our type inheritance for both 'struct' and for flat 'union' merges
    key/value pairs from the base class with those from the type in
    question.  Although the C code currently boxes things so that there
    is a distinction between which member is referred to, the QMP wire
    format does not allow passing a key more than once in a single
    object.  Besides, if we ever change the generated C code to not be
    quite so boxy, we'd want to avoid duplicate member names there,
    too.
    
    Fix a testsuite entry added in an earlier patch, as well as adding
    a couple more tests to ensure we have appropriate coverage.  Ensure
    that collisions are detected, regardless of whether there is a
    difference in opinion on whether the member name is optional.
    Signed-off-by: NEric Blake <eblake@redhat.com>
    Reviewed-by: NMarkus Armbruster <armbru@redhat.com>
    Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
    ff55d72e
struct-base-clash-deep.err 93 字节