Expose ConfigBuilder::crypto_provider()#2181
Conversation
Benchmark resultsInstruction countsSignificant differencesClick to expand
Other differencesClick to expand
Wall-timeSignificant differencesClick to expand
Other differencesClick to expand
Additional informationCheckout details:
|
3c7ad04 to
40694f8
Compare
|
Does this need some test coverage? Where/how? |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2181 +/- ##
==========================================
+ Coverage 94.72% 94.79% +0.07%
==========================================
Files 102 102
Lines 23753 24468 +715
==========================================
+ Hits 22499 23195 +696
- Misses 1254 1273 +19 ☔ View full report in Codecov by Sentry. |
|
I think this is semver-compatibility failure is probably not a big deal: (Especially since in practice, all instances of |
cpu
left a comment
There was a problem hiding this comment.
I trust your evaluation of the semver reporting 👍
I think it wouldn't hurt & seems like an easy lift. Maybe update these two tests to save the |
40694f8 to
4bb9107
Compare
|
Added tests sort of like you suggested. |
This enables downstream projects (such as rustls-platform-verifier -- see rustls/rustls-platform-verifier#150) to get the
CryptoProviderfrom theConfigBuilder, instead of having to pick one in parallel.