hashhash function should be a standalone library importing C impl of sha3 and tiny-keccak (for updatable sha3s)vector::*util subcrates~ (controversial)I'm not convinced about flattening util subcrates. Why not group non-blockchain-specific utilities within a single folder?
ok, let's keep all subcrates in util directory for now. We'll discuss it again someday
I'll take
- [ ] replace sha3::Hashable trait and all of usages of it with a simple function called `hash`
- [ ] this `hash` function should be a standalone library importing C impl of sha3 and tiny-keccak (for updatable sha3s)
Also fixed hash should be crates.io library dependant on bigint and little more
I'll take util should not reexport HeapSizeOf for now
I will take triehash should be separated from util
I'll take util should not reexport bigint
I'll take util should not reexport ansi_term if you guys don't mind:)
I'll take one more: util should not reexport ParkingLot.
@Hawstein thanks, merged!
I will take timer::PerfTimer should be a part of ethcore.
I will take semantic_version should be separated from util.
I will take
@debris Should I move the journaldb, migration and trie out of util/src dir and put them in the util/ dir just like other libs. Seems that this is a reasonable way to arrange them.
@debris Should I move the
journaldb,migrationandtrieout ofutil/srcdir and put them in theutil/dir just like other libs. Seems that this is a reasonable way to arrange them.
@Hawstein yes, this would be a great first step. Eventually, we would also like to decouple journaldb and rocksdb :)
@debris they are already decoupled to some degree via the KeyValueDB trait.
I will take error::UtilError should be replaced by error_chain
@debris Hi, I am working on the all trie traits from util should be separated from util. Since it depends lots of stuffs in util/src, so I decide to move all the *.rs file in util/src out of the src dir and make it a lib. It needs to be done for other tasks too. Does it make sense for you?
@Hawstein yes, I believe it's one of the last things needed ;)
@debris Great! Then I will take the following tasks too:
Since once I make those *.rs files into a lib, the above tasks are almost done.
Most helpful comment
@debris Great! Then I will take the following tasks too:
Since once I make those
*.rsfiles into a lib, the above tasks are almost done.