This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Move async remove to snapshot_utils.rs #29406
Merged
xiangzhu70
merged 1 commit into
solana-labs:master
from
xiangzhu70:move_async_remove_to_snapshot_utils
Jan 3, 2023
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
nit: Why did we reverse the order of these functions? All the other pub/helper pairs in this file are in the order: pub first, helper(s) immediately below.
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 copied the whole block from validator.rs to this file. I guess there is no such order convention in that file. I can reverse it here. But I think this kind of convention does not matter, and is hard to maintain. When a function is changed from private to public, is there need to generate a big diff just to maintain this order?
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 the diff it looks like in
core/src/validator.rs
the order of functions ismove_and_async_delete_path()
delete_contents_of_path()
And in
runtime/src/snapshot_utils.rs
the order is nowdelete_contents_of_path()
move_and_async_delete_path()
My interpretation of @apfitzge's question is "why change this order?"
I understand/agree that there is not a convention/requirement for function ordering, and agree that public to private should not generate a large diff. In this case, the diff for moving code between files will be large no matter what. It's a tiny bit easier to review the diff if the function ordering does not change though.
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.
Yeah, was just wondering why the order did get reversed. I tried checking the new vs old blocks by just ctrl-Fing the entire moved code block, which failed due to the fn re-ordering.