enumsA Rust enum is mapped to an opaque C++ type.
To receive C++ bindings, the enum must be movable in C++. See Movable Types.
Given the following Rust crate:
{{ #include ../../examples/rust/enum/example.rs }}
Crubit will generate the following bindings:
{{ #include ../../examples/rust/enum/example_generated.h }}
enum? {#cpp_enum}A repr(i32) or fieldless repr(C) enum is very similar to a C++ enum. However, Rust enums are exhaustive: any value not explicitly listed in the enum declaration does not exist, and it is undefined behavior to attempt to create one.
C++ enums, in contrast, are “non-exhaustive”: a C++ enum can have any value supported by the underlying type, even one not listed in the enumerators. For example, if the above example were a C++ enum, static_cast<Color>(42) would be a valid instance of Color, even though neither Red, Blue, nor Green have that value.
In order to prevent invalid Rust values from being produced by C++, a C++ enum cannot be used to represent a Rust enum. Instead, the C++ bindings are a struct, even for fieldless enums.
To receive C++ bindings, the enum must be movable in C++. See Movable Types.
Each variant of a Rust enum may contain an additional payload (a tuple or a struct). C++ bindings for Rust enums provide the following ways of working with an enum payload:
Constructing an enum variant with the given payload by calling a static Make<variant name> method (one such method is injected for each of enum variants). The following bugs track future work in this area:
constexprTODO(b/262737383): Matching enum variants and inspecting their payload.
Given the following Rust crate:
{{ #include ../../examples/rust/enum_with_payload/example.rs }}
Crubit will generate the following bindings:
{{ #include ../../examples/rust/enum_with_payload/example_generated.h }}