-
Notifications
You must be signed in to change notification settings - Fork 831
Rename inner key field in PrivateKey and PublicKey #762
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
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.
ffe7ecc47ef6145e11c166cff155afc2acb81bfb. The error is not as bad downstream. Should not be hard for people to debug.
|
61 | println!("{:?}", public_key.key);
| ^^^ unknown field
|
= note: available fields are: `compressed`, `inner`
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.
I'm not certain doing this is a good idea (was avoiding inner
word lately) but
ACK ffe7ecc47ef6145e11c166cff155afc2acb81bfb
the code itself. Do as you wish.
Rebased |
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 b7ed6669eba733750a4c8b4ec75f22aa1cdacebf
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 b7ed6669eba733750a4c8b4ec75f22aa1cdacebf
I like this. Typing key.key
everywhere was pretty confusing.
Hm, is this ready for the merge? Do not want to merge my own PRs by myself. |
Let's wait for one more ACK since @Kixunil was so hesitant. |
This will conflict with many of the open PRs. Should we first merge this or merge this as the last PR before the release? What do you think @dr-orlovsky |
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 ffe7ecc
@sanket1729 lets merge them first, they were much harder and longer to review |
eb09019
Now, let's merge this one, after which I will re-base both #696 and #757, which have just a single ACK and have to be re-based anyway now. @apoelstra @sanket1729 @Kixunil pls re-ack |
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 eb09019
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 eb09019
Since we already broke all possible key-related APIs with this release, I think this one is good to have with 0.28.
Closes #532