Eric Blake writes:
> On 04/13/2016 06:48 AM, Markus Armbruster wrote:
>> Eric Blake writes:
>>
>>> Rather than having two separate visitor callbacks with items
>>> already broken out, pass the actual QAPISchemaObjectType object
>>> to the visitor. This lets the visitor access things like
>>> t
On 04/13/2016 06:48 AM, Markus Armbruster wrote:
> Eric Blake writes:
>
>> Rather than having two separate visitor callbacks with items
>> already broken out, pass the actual QAPISchemaObjectType object
>> to the visitor. This lets the visitor access things like
>> type.is_implicit() without nee
Eric Blake writes:
> Rather than having two separate visitor callbacks with items
> already broken out, pass the actual QAPISchemaObjectType object
> to the visitor. This lets the visitor access things like
> type.is_implicit() without needing another parameter, resolving
> a TODO from previous
Rather than having two separate visitor callbacks with items
already broken out, pass the actual QAPISchemaObjectType object
to the visitor. This lets the visitor access things like
type.is_implicit() without needing another parameter, resolving
a TODO from previous patches.
For convenience and c
