Eric Blake 74da8f0eea qapi: Forbid 'any' inside an alternate ... The whole point of an alternate is to allow some type-safety while still accepting more than one JSON type. Meanwhile, the 'any' type exists to bypass type-safety altogether. The two are incompatible: you can't accept every type, and still tell which branch of the alternate to use for the parse; fix this to give a sane error instead of a Python stack trace. Note that other types that can't be alternate members are caught earlier, by check_type(). Backports commit 46534309e667fd860720f983c2c9aefe0354340d from qemu		2018-02-20 15:47:16 -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: Drop unused 'kind' for struct/enum visit	2018-02-19 23:43:54 -05:00
qapi-types.py	qapi: Swap visit_* arguments for consistent 'name' placement	2018-02-19 22:45:07 -05:00
qapi-visit.py	qapi-visit: Honor prefix of discriminator enum	2018-02-20 15:38:44 -05:00
qapi.py	qapi: Forbid 'any' inside an alternate	2018-02-20 15:47:16 -05:00