Own error type

[leonjia0112]

Would it be better if there is an error type for our own crate that can map from other error? (e.g. Fromio::Errror, etc)

Because now the err handling type is a boxed string, which looks not professional. :)

[frozencemetery]

(Per out-of-band conversation, this is a good idea.)

[lukehinds]

Likely another one that can be closed (based on the merged PR above)

[frozencemetery]

@mbestavros how close are you on this?

[mbestavros]

I've got a basic custom error for crypto.rs working on my end. I'm currently hashing out the best way to wrap ErrorStack errors thrown by rust-openssl; once that's done, I'll integrate them into the existing bindings and push for review.

[mbestavros]

@frozencemetery and @lukehinds: The above two PRs (#49 and #52) implement a custom error type for crypto.rs and adjust the return types of the functions introduced in #43, as specified. Unless we'd like to keep this issue open to encapsulate other potential custom errors elsewhere in the codebase, I think this is fair game to be resolved.

(Personally, I think it'd make more sense to open separate issues for other custom error types, should we want to pursue them.)

[frozencemetery]

Agreed, closing.