-
Notifications
You must be signed in to change notification settings - Fork 1.7k
ethkey and ethstore use hash structures from bigint #1851
Conversation
needs a merge |
@@ -156,59 +156,5 @@ pub use log::*; | |||
pub use kvdb::*; | |||
pub use timer::*; | |||
|
|||
#[cfg(test)] |
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.
how the code below related to the pr topic?
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.
ahh... you are right. this test was just moved to different file `util/bigint/src/uint.rs', cause it fits there better
@@ -19,7 +19,7 @@ | |||
use std::str::FromStr; | |||
use serde::{Deserialize, Deserializer, Error}; | |||
use serde::de::Visitor; | |||
use util::hash::{H64 as Hash64, Address as Hash160, H256 as Hash256, H2048 as Hash2048}; | |||
use util::hash::{H64 as Hash64, H160 as Hash160, H256 as Hash256, H2048 as Hash2048}; |
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.
prefer to stick to Address
over H160
as long as it's being used for an address.
unless we're actually using a 160-bit datum for something generic, then it should be named |
I agree. I just renamed usages of |
in next pr, I will remove duplicated signing logic (it's in ethkey and util/crypto)