-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
update transaction_outputs #20456
update transaction_outputs #20456
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
Thanks @xiaodi007 for the change. There's one clippy suggestion that we need to apply to make the CI green. |
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.
@stefan-mysten maintain the received_objects
without .into_iter()
, Thanks a lot !
@stefan-mysten Hi, could you please take a look to see if anything else needs to be revised? |
Thanks @xiaodi007. @mlogan is not around this week, so just waiting for him to confirm this is OK and be aware of the needed fix in our dashboard. Give me a bit more time before landing this, thank you! |
Got it, thanks! |
Co-authored-by: stefan-mysten <[email protected]>
Description
possible_to_receive.iter().clone()
->possible_to_receive.into_iter()
:This modification is generally appropriate and improves performance by avoiding unnecessary cloning of the
possible_to_receive
collection. Instead of cloning, it consumes the iterator, which is more efficient..chain(received_objects)
->.chain(received_objects.into_iter())
:By calling
into_iter()
onreceived_objects
when adding them tolocks_to_delete
, the objects are directly used in the collection and the original reference toreceived_objects
is no longer necessary.transaction_orchestrator
**:fnished
->finished
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.