Adds add_uniffi_exported_parser
macro
#87
Merged
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.
Builds on #85. We use custom parsers that we export through UniFFI, so consumers can use the correct parser for the response type. However, all our parsers' signatures are identical, with the only change being the return type and it adds a lot of boilerplate.
This PR introduces the convenience macro
add_uniffi_exported_parser!
that generates these functions - we just need to pass a name and return type to it. Besides the decreased noise in the code, this should help us ensure that we are building our parsers in a consistent manner.Note that this will not result in any change to the code that we are executing, it's just a syntactic sugar.