-
Notifications
You must be signed in to change notification settings - Fork 51
Add no_std support
#52
Conversation
This was saving a very small amount of code and will make it difficult to refactor the `write` function into the `input` function in the next commit.
|
Rebased, fixed build failure with |
|
Removed redundant fuzztarget/nonfuzztarget |
|
Is there a specific reason why you implemented input for each hash instead of using a macro like there was for Otherwise ACK. |
|
It was just short, and all the duplication was in one file right next to each other. If I need to change it I'll convert it to a macro. |
|
Added a commit to bump the version number. @sgeisler am I ok to merge? |
|
If anyone really wants the |
dongcarl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably cherry-pick dongcarl@01ae9cb for proper propagation of {no_,}std, can also cherry-pick dongcarl@4ac63b7
This was previously removed to aid restructuring, but should be added back so we don't have to remember to modify every HashEngine every time we modify the input function.
|
cherry-picked both. Thanks! |
|
ACK eac6cde |
When
no_stdis on we lose theio::Writeimpls on all the hash engines, naturally, as well as thestd::error::Errorimpl onError.We also lose the
ToHextrait, since this outputs aString, though we retain theformat_hexfunction as well asfmt::{Display, LowerHex, UpperHex}for all hashes.Fixes #12