From ee3b8c267d34d655cb64a7e60c6f7f6ba8bbce28 Mon Sep 17 00:00:00 2001 From: Tobin Harding Date: Wed, 9 Mar 2022 10:22:36 +1100 Subject: [PATCH] Order impl_hashencode lines Put the calls to `impl_hashencode` in the same order, and with the same whitespace, as the calls to `hash_newtype`. This makes groking the file easier because its quick to glance down the types and see which ones implement hashencode (consensus_encode/decode) and which ones do not. --- src/hash_types.rs | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/hash_types.rs b/src/hash_types.rs index 253d993b..19a59c9a 100644 --- a/src/hash_types.rs +++ b/src/hash_types.rs @@ -60,9 +60,11 @@ hash_newtype!(FilterHeader, sha256d::Hash, 32, doc="Filter header, as defined in impl_hashencode!(Txid); impl_hashencode!(Wtxid); -impl_hashencode!(SigHash); impl_hashencode!(BlockHash); +impl_hashencode!(SigHash); + impl_hashencode!(TxMerkleNode); impl_hashencode!(WitnessMerkleNode); + impl_hashencode!(FilterHash); impl_hashencode!(FilterHeader);