Marc-André Lureau <[email protected]> writes:
[Possible improvement to the QAPI/QMP QOM introspection interface...]
>> Thoughts?
>
> I like it overall.
>
> But this goes beyond the intended scope of the series.
> Blending/merging QOM type & QAPI type would warrant more design
> research. So covering child<> & link<> are out of scope of the current
> qom-qapi series. I think the addition of qapi-type shouldn't be
> incompatible with a future proposal, after all all properties should
> have some 'wire' type (link/child are paths). But we can drop it for
> now or just rename it x-qapi-type until we agree on the new
> introspection.
>
> my2c
Adding @qapi-type with feature unstable means we don't have to worry
about the external interface now. One less hurdle for merging. I like
it.
Whether changing the @type values is safe remains somewhat unclear. See
Subject: Property types changed in this series (was: [PATCH v7 00/65] Hi)
Date: Wed, 21 Oct 2026 18:29:40 +0200
Message-ID: <[email protected]>
