Eric Blake a7713451d9 qapi: Assert in places where variants are not handled ... 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. Backports commit 29f6bd15eb8a55ed37b2a443f7275b3d134eb2b2 from qemu		2018-02-21 21:58:29 -05:00
..
create_config	more cleanup qemu/configure	2017-01-19 14:11:54 +08:00
make_device_config.sh	fix file perms	2015-08-28 21:05:38 -07:00
ordereddict.py	import	2015-08-21 15:04:50 +08:00
qapi-event.py	qapi: Assert in places where variants are not handled	2018-02-21 21:58:29 -05:00
qapi-types.py	qapi: Don't box branches of flat unions	2018-02-20 16:44:55 -05:00
qapi-visit.py	qapi: Don't box branches of flat unions	2018-02-20 16:44:55 -05:00
qapi.py	qapi: Don't box struct branch of alternate	2018-02-20 16:32:11 -05:00