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
Wrap transactions as
Arc<Transaction>
inTxGraph
#1373Wrap transactions as
Arc<Transaction>
inTxGraph
#1373Changes from all commits
8ab58af
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.
Interested to understand why this
&
is needed now. Before tx was of typeTransaction
right, so shouldn't it needed to have been borrowed before?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.
Before,
TxNode
'stx
field is of a reference toT
. I changed it in this PR to just betx: T
. Note thatT
is nowArc<Transaction>
.Because
sent_and_received
takes in a&Transaction
, we expect to call.as_ref
onArc<Transaction>
. However, we can make use of the auto-deref properties ofAsRef
implementations (such asArc
), so just doing&tx
is enough.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.
Maybe we can map to shared ref
&
internally and avoid returningArc<Transaction>
inget_tx{_node}
On second thought, the PR description implies that we specifically DO want to return an arc pointer.
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.
Yes, I think we should return a concrete
Arc
for this API to be useful (cheaply share transactions between chain-source, receiving-structs and changesets).