-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
merge #12752, #10785, #17896, #17957, #18021, #18112: serialization improvements #4037
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.
Not sure if I like skipping commits here, would be nice to finalize these backports while we are at it... But LGTM otherwise, so
utACK
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.
One nit see below and i also feel like we shouldn't just randomly skip commits while backporting PRs only because they are "not relevant". There is imo no good reason to only partially backport PRs if its possible to completely merge them in.. skipping parts of them just makes reviewing the PR as a whole a bit weird/confusing here and there imo and this even two times, now and when backporting the remaining parts.
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.
slightly tested 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
please resolve conflicts |
@UdjinM6 is this merge okay, or does it need to be a rebase? |
¯\_(ツ)_/¯ Personally, I'd prefer a rebase but technically this merge should be ok too I guess |
bitcoin@9250a08 Partial bitcoin#17850: Introduce new serialization macros without casts bitcoin@ca33451
bitcoin@9b66083 Partial bitcoin#17896: Convert VARINT to the formatter/Using approach bitcoin@2f1b2f4 Partial bitcoin#17896: Add a generic approach for (de)serialization of objects bitcoin@ca62563
bitcoin@3c94b00 Partial bitcoin#18021: Make std::vector and prevector reuse the VectorFormatter logic bitcoin@3cd8ab9 Partial bitcoin#18021: Add custom vector-element formatter bitcoin@abf8624 Partial bitcoin#18021: Add a constant for the maximum vector allocation (5 Mbyte) 37d800b
…work bitcoin@4de934b Partial bitcoin#17957: Add FORMATTER_METHODS, similar to SERIALIZE_METHODS, but for formatters bitcoin@ca34c5c
…amework bitcoin@353f376 Partial bitcoin#18112: Add CustomUintFormatter bitcoin@e574fff Partial bitcoin#18112: Add DifferenceFormatter bitcoin@1063339 Partial bitcoin#18112: Make VectorFormatter support stateful formatters bitcoin@56dd9f0 Partial bitcoin#18112: Convert CCompactSize to proper formatter bitcoin@3ca574c
Yeah, I prefer rebase I think. @kittywhiskers please see https://github.com/PastaPastaPasta/dash/commits/pr_4027 I rebased on develop and squashed your commits |
Branch updated with @PastaPastaPasta's fork as-is |
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, although should probably adjust title
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
Overview
As part of #4025, component pull requests that are required by TorV3 logic are being broken down into branches wherever feasable. This PR deals with serialization improvements taken from bitcoin#10785 (split into bitcoin#17850, bitcoin#17896, bitcoin#17957, bitcoin#18021, bitcoin#18112 and others)
Contents
9250a08 has been skipped for the sake of brevity, not relevant to partial #8149 and merge #19845, #19954: Complete the BIP155 implementation and upgrade to TORv3 #4025Resolved in 7396f359b66083 has been skipped for reasons mentioned aboveResolved in bbe9c254de934b has been skipped as it presumes the presence of bitcoin@d2d7267Resolved in 6e129993c94b00 is skippedResolved in 5bd678d353f376 skpdResolved in 9036875