| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
Having one function that does both seems to be measurably faster, though
I would have expected the compiler to inline and generate comparable
assembly. Well, seems it didn't.
|
| |
|
|
|
|
| |
There are now 2 features that control the amount of precomputed
constants. They can either be 0, 12, or 256. Most users will likely want
to go with the 12, so this is the default feature.
|
| |
|
|
|
| |
It seems English doesn't use the word potency in this context, but
rather uses power.
|
| |
|
|
|
|
|
|
|
|
|
| |
The maximum power of the base that can fit into a given data type is
constant. There's no point in computing it at runtime, if we can just
store it in a compile-time constants array.
The code isn't the most beautiful, but that's mostly because Rust const
functions are still a bit limited.
One function was duplicated, because it was easy to get a slow version
to compile in const context, and const context doesn't really care...
|
| |
|
|
|
| |
Speeds up the 20 and 32 byte cases. Has slightly negative impact for 16
byte case.
|
| | |
|
| | |
|
| | |
|
|
|
Moved the basis conversion into a submodule, to ease the upcoming
rewrite.
Add a couple of new integration tests.
Fix a bug caused by misreading the PasswordMaker Pro HMAC code.
|
