The issue is that the library can't know what state the program is running in, since it's a library... it has a job to perform some crypto functionality and it can only either return a result or an error for that particular operation.

When libraries start calling abort out of the blue it's like the janitor deciding to send everyone home for the day because their mop broke. It's not their call to make :)

Panicking or any other error handling mechanism which permits the main application to decide how to continue is perfectly fine.

> Infinitely better to crash than to potentially let the process/library run in some kind of degraded state.

Why? Just set the entire library to "failed" mode and have every function return an error or do nothing from that point forward. That is far more sensible than just panicking and bringing down the entire application.

Imagine if people want to use this in a cash machine or something like that.