Eric Blake writes:
> On 08/04/2015 02:18 AM, Markus Armbruster wrote:
>> A command's or event's 'data' must be a struct type, given either as a
>> dictionary, or as struct type name.
>>
>> Commit dd883c6 tightened the checking there, but not enough: we still
>> accept 'union'. Fix to reject it.
On 08/04/2015 02:18 AM, Markus Armbruster wrote:
> A command's or event's 'data' must be a struct type, given either as a
> dictionary, or as struct type name.
>
> Commit dd883c6 tightened the checking there, but not enough: we still
> accept 'union'. Fix to reject it.
>
> We may want to support
On 08/04/2015 03:18 AM, Markus Armbruster wrote:
> A command's or event's 'data' must be a struct type, given either as a
> dictionary, or as struct type name.
>
> Commit dd883c6 tightened the checking there, but not enough: we still
> accept 'union'. Fix to reject it.
>
> We may want to support
A command's or event's 'data' must be a struct type, given either as a
dictionary, or as struct type name.
Commit dd883c6 tightened the checking there, but not enough: we still
accept 'union'. Fix to reject it.
We may want to support union types there, but we'll have to extend
qapi-commands.py a
