Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
txnbuild: Reinstate missing fee bump transaction functions #3199
txnbuild: Reinstate missing fee bump transaction functions #3199
Changes from 2 commits
4830b5c
50efba2
5ffba04
d03b5d3
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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 know you're just reinstating missing functionality, but can I ask what this is doing? Is this like a Go-idiomatic way to copy a struct?
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.
in Go the assignment operator copies by value. However, the assignment operator does a shallow copy. If you have any pointers or slices in your structs, the new struct will still have references to those fields. Here's an article which provides more details on this topic https://flaviocopes.com/go-copying-structs/
In this particular case, the signatures field is the only mutable field in the struct. There are no exported functions on
FeeBumpTransaction
orTransaction
which modify any of the other fields in the struct. The code creates a copy of theFeeBumpTransaction
struct via assignment and then it does a deep copy on the signatures slice.