Eric Blake dc65960e1f qapi: Don't use info as witness of implicit object type ... A future patch will enable error reporting from the various QAPISchema*.check() methods. But to report an error related to an implicit type, we'll need to associate a location with the type (the same location as the top-level entity that is causing the creation of the implicit type), and once we do that, keying off of whether foo.info exists is no longer a viable way to determine if foo is an implicit type. Instead, add an is_implicit() method to QAPISchemaEntity, and use it. It can be overridden later for ObjectType and EnumType, when implicit instances of those classes gain info. Backports commit 49823c4b4304a3e4aa5d67e089946b12d6a52d64 from qemu		2018-02-19 18:53:06 -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: Share gen_visit_fields()	2018-02-19 18:41:41 -05:00
qapi-types.py	qapi: Don't use info as witness of implicit object type	2018-02-19 18:53:06 -05:00
qapi-visit.py	qapi: Don't use info as witness of implicit object type	2018-02-19 18:53:06 -05:00
qapi.py	qapi: Don't use info as witness of implicit object type	2018-02-19 18:53:06 -05:00