Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

expose Schnorrkel Error from mc-crypto-keys #3261

Merged
merged 3 commits into from
Mar 20, 2023
Merged

Conversation

cbeck88
Copy link
Contributor

@cbeck88 cbeck88 commented Mar 20, 2023

This type is already exposed in public APIs of RistrettoPublic and various conversions, but it is not actually exported from the crate, so there is no way for downstream to name the type.

This commit re-exports the type at crate level, which is already part of the public API anyways.

This type is already exposed in public APIs of RistrettoPublic and
various conversions, but it is not actually exported from the crate,
so there is no way for downstream to name the type.

This commit re-exports the type at crate level, which is already
part of the public API anyways.
@cbeck88 cbeck88 requested review from jcape, a team and nick-mobilecoin and removed request for a team March 20, 2023 04:16
Copy link
Collaborator

@nick-mobilecoin nick-mobilecoin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious what the use case is?

I may have missed other places, but this looks to be used in 3 places:

@cbeck88
Copy link
Contributor Author

cbeck88 commented Mar 20, 2023

I have a service that calls verify_schnorrkel and I need to do things like implement From<SchnorrkelError> for Error.

It seems to me that there's no good reason that I shouldn't be able to do this. That's the idiom we typically use for stuff like this.

@cbeck88 cbeck88 merged commit 3bcdb7d into master Mar 20, 2023
@cbeck88 cbeck88 deleted the expose-schnorrkel-error branch March 20, 2023 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants