1. 18 3月, 2016 1 次提交
    • E
      qapi: Assert in places where variants are not handled · 29f6bd15
      Eric Blake 提交于
      We are getting closer to the point where we could use one union
      as the base or variant type within another union type (as long
      as there are no collisions between any possible combination of
      member names allowed across all discriminator choices).  But
      until we get to that point, it is worth asserting that variants
      are not present in places where we are not prepared to handle
      them: when exploding a type into a parameter list, we do not
      expect variants.  The qapi.py code is already checking this,
      via the older check_type() method; but someday we hope to get
      rid of that and move checking into QAPISchema*.check().  The
      two asserts added here make sure any refactoring still catches
      problems, and makes it locally obvious why we can iterate over
      only type.members without worrying about type.variants.
      Signed-off-by: NEric Blake <eblake@redhat.com>
      Message-Id: <1458254921-17042-2-git-send-email-eblake@redhat.com>
      Signed-off-by: NMarkus Armbruster <armbru@redhat.com>
      29f6bd15
  2. 17 3月, 2016 39 次提交