-
Notifications
You must be signed in to change notification settings - Fork 28
Remove deprecated std pair wrappers #11
Remove deprecated std pair wrappers #11
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 4f3d7f4
f6e2da0
to
50cd05a
Compare
Rebased now that #11 has been merged. @MarcoFalke - do you mind reviewing? Should be trivial. |
50cd05a
to
85052a4
Compare
Should be trivially reviewable. Just apply this patch to |
utACK 85052a4 |
Just noting for completeness, that this would break other downstream projects (if there are any). Effectively we'd have to tag a release before this breaking change and then mark this as a breaking change when tagged a version that includes this change. Though, it doesn't seem we do proper releases (or tags) at all, so I think this is nothing to worry about. |
utACK 85052a4 |
@achow101, @fanquake, @instagibbs, @sipa - this would have prevented the |
Imo this is ready for merge |
ACK 85052a4 |
utACK 85052a4 |
@laanwj - I think this is ready for merge |
85052a4 Remove deprecated std::pair wrappers (Karel Bilek) Pull request description: These are deprecated and no longer used in Bitcoin Core. Tree-SHA512: 774c9b84f88e0c5e2062b3d7f03399d9909830d044bc3cf8dfcd45e58f48072ce527f471360cb36594e898e625d965b71436559bff2bb4b368255b9f1e26f722
Uh, NACK? As @MarcoFalke noted, this breaks the API... This isn't a Bitcoin Core project. Releases are upstream. |
There is no univalue release with these changes included, so there is nothing broken. We'd only have to "[...] mark this as a breaking change when tagged a version that includes this change." Note that the subtree bump in the bitcoin core repo is only a "stylistic" change to prevent devs from using the deprecated wrappers. (Sort of a linter) |
These are deprecated and no longer used in Bitcoin Core.