qapi/schema: add _check_complete flag
authorJohn Snow <jsnow@redhat.com>
Fri, 15 Mar 2024 15:22:51 +0000 (16:22 +0100)
committerMarkus Armbruster <armbru@redhat.com>
Wed, 24 Apr 2024 08:03:54 +0000 (10:03 +0200)
commit875f6242321a63b3599e0cf6f0694adf8d855799
tree1ca4c83bb9d61a06307002f87069dbd71e4aa898
parent8b9e7fd3b38d4e0fb9311752a5b44b71cd8fbbc1
qapi/schema: add _check_complete flag

Instead of using the None value for the members field, use a dedicated
flag to detect recursive misconfigurations.

This is intended to assist with subsequent patches that seek to remove
the "None" value from the members field (which can never hold that value
after the final call to check()) in order to simplify the static typing
of that field; avoiding the need of assertions littered at many
callsites to eliminate the possibility of the None value.

Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Message-ID: <20240315152301.3621858-16-armbru@redhat.com>
scripts/qapi/schema.py