diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2024-11-29 15:19:23 +0100 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-12-19 19:36:37 +0100 |
commit | 6dd818fbbbe3efc63889e7d811ac6b70e788c629 (patch) | |
tree | 505c2bd4d37efaa56db693a6e9ee1f6e627b44cb /rust/qemu-api-macros | |
parent | b1987a2547c8e32fd3c32f504fe8d4bc58b7f961 (diff) | |
download | qemu-6dd818fbbbe3efc63889e7d811ac6b70e788c629.zip qemu-6dd818fbbbe3efc63889e7d811ac6b70e788c629.tar.gz qemu-6dd818fbbbe3efc63889e7d811ac6b70e788c629.tar.bz2 |
rust: qom: put class_init together from multiple ClassInitImpl<>
Parameterize the implementation of ClassInitImpl so that it is
possible to call up the chain of implementations, one superclass at
a time starting at ClassInitImpl<Self::Class>.
In order to avoid having to implement (for example)
ClassInitImpl<PL011Class>, also remove the dummy PL011Class and
PL011LuminaryClass structs and specify the same ObjectType::Class as
the superclass. In the future this default behavior can be handled by
a procedural macro, by looking at the first field in the struct.
Note that the new trait is safe: the calls are started by
rust_class_init<>(), which is not public and can convert the class
pointer to a Rust reference.
Since CLASS_BASE_INIT applies to the type that is being defined,
and only to it, move it to ObjectImpl.
Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'rust/qemu-api-macros')
0 files changed, 0 insertions, 0 deletions