Eric Blake writes:
> On 06/16/2016 08:46 AM, Markus Armbruster wrote:
>> Markus Armbruster writes:
>>
>>> Eric Blake writes:
>>>
Rather than having two separate visitor callbacks with items
already broken out, pass the actual QAPISchemaObjectType object
to the visitor. This let
On 06/16/2016 08:46 AM, Markus Armbruster wrote:
> Markus Armbruster writes:
>
>> 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 li
Markus Armbruster writes:
> 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
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
