Support mapping Enums to Result type #3102
Open
+269
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some enums, where the Ok variant is 0, can be mapped to a Rust
Result<(), NonZero<NewType>>
representation, where the enum newtype is generated without the Ok variant.This PR adds a new option for the user to select this new Result representation for the enum, which can make the generated APIs more ergonomic, when C functions use the result enum as their return type.
Additionally, a parse callback is added, which allows renaming the new error enum (which does not contain the Ok / 0 variant).
As discussed in the linked issue, since Rust currently doesn't allow arbitrary niches, this new enum mapping can only work with C result enums, where 0 is the Ok value. Other error enums are out of scope.
Closes #2980