We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I think OpenSSL is useful for cross-testing (see #635) but I find the benchmark are annoying:
benchmark_verify
I think the benchmarks were useful in the early days of this library to demonstrate that it outperforms OpenSSL but this not necessary anymore.
Do people agree that we should remove them?
The text was updated successfully, but these errors were encountered:
I'm fine with it. But I think I'll look into implementing #716 this week to completely remote openssl
Sorry, something went wrong.
ACK (independent of whether we also get rid of the OpenSSL tests or not)
resolved by #983
No branches or pull requests
I think OpenSSL is useful for cross-testing (see #635) but I find the benchmark are annoying:
benchmark_verify
is a special case in the build, see build: fix OpenSSL EC detection on macOS #735.I think the benchmarks were useful in the early days of this library to demonstrate that it outperforms OpenSSL but this not necessary anymore.
Do people agree that we should remove them?
The text was updated successfully, but these errors were encountered: