Expose the inner rust side error type via the exception on the c++ side #1063
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.
This is an attempt to address #870 and similar issues.
I attempt to expose more information on the underlying rust error by including the the original error into the c++ side exception. This allows accessing any error related information from the c++ side as well, assuming that the error type is exposed as part of the cxx bridge definition.
I deliberately open this PR in this state, to gather some feedback on the design idea before spending to much time on details.