-
Notifications
You must be signed in to change notification settings - Fork 624
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
Why do we have two SigHashType
s?
#670
Comments
|
Sorry, my previous comment was pertinent but not the real reason, the real reason it's the |
Can we somehow differentiate them by name, do a deprecated stuff on the old one or add necessary doc explanations on the choice of the structure? |
Lol, let's just remove the one in |
If we do so, we would have to add checks to existing methods to not use the new variants. At which I think that having two separate types is the correct thing. |
If we have to maintain both structures we need to differentiate them by name and clearly describe the purpose of both in the docs |
Also, I think we are re-exporting the legacy one Line 125 in a961ab4
|
First one:
https://github.com/rust-bitcoin/rust-bitcoin/blob/master/src/blockdata/transaction.rs#L676-L695
Second one:
https://github.com/rust-bitcoin/rust-bitcoin/blob/master/src/util/sighash.rs#L102-L126
The text was updated successfully, but these errors were encountered: