-
Notifications
You must be signed in to change notification settings - Fork 714
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Wallet] Remove (explicitely) unused tx comparator #939
Conversation
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.
utACK 1f224d3
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.
utACK 1f224d3
We remove the '==' and '!=' operators from CMutableTransaction. These comparators are never explicitely used in our code. As it turns out, it was used implicitely and created this situation: PIVX-Project#510 So this change fixes PIVX-Project#510.
Rebased without change (to pass travis after #943 being merged). |
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.
ACK 3da857b
3da857b [Wallet] Remove (explicitely) unused tx comparator (warrows) Pull request description: '==' and '!=' operators in CMutableTransaction are never used explicitly. Them being used implicitly is probably what causes #510. There is no good reason to keep them and BTC removed them here: bitcoin#13443 Should fix #510 ACKs for top commit: Fuzzbawls: ACK 3da857b Tree-SHA512: f5874d794b0a43b1290c977b10d16b1a8078b09862886f34bcdcc65e5a1ef2b9eb1c3e43dfe4711861609cf5a6c92d35180e37a95f5d5afcbac16854d5189dee
We remove the '==' and '!=' operators from CMutableTransaction. These comparators are never explicitely used in our code. PIVX-Project/PIVX#939
'==' and '!=' operators in CMutableTransaction are never used explicitly.
Them being used implicitly is probably what causes #510. There is no good reason to keep them and BTC removed them here: bitcoin#13443
Should fix #510