Skip to content

Conversation

@tarcieri
Copy link
Member

There are several places where errors aren't expected to happen which previously used expect to raise panics in these cases.

This means that the pkcs8 crate is not panic-free in these cases. Many of them are handled more cleanly with ensured error propagation without the use of expect.

Consumers of this crate who would like infallible APIs can call expect themselves in these cases.

There are several places where errors aren't expected to happen which
previously used `expect` to raise panics in these cases.

This means that the `pkcs8` crate is not panic-free in these cases. Many
of them are handled more cleanly with ensured error propagation without
the use of `expect`.

Consumers of this crate who would like infallible APIs can call `expect`
themselves in these cases.
@tarcieri tarcieri force-pushed the pkcs8/replace-expect-with-fallible-methods branch from dd85069 to 0c0f36e Compare October 15, 2021 20:56
@tarcieri tarcieri merged commit d4bc1e3 into master Oct 15, 2021
@tarcieri tarcieri deleted the pkcs8/replace-expect-with-fallible-methods branch October 15, 2021 20:58
@tarcieri tarcieri mentioned this pull request Nov 16, 2021
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.

2 participants