-
Notifications
You must be signed in to change notification settings - Fork 5
feat: some fixes #105
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
Open
SWvheerden
wants to merge
3
commits into
tari-project:main
Choose a base branch
from
SWvheerden:sw_fix_scanning
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+25
−24
Open
feat: some fixes #105
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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 hidden or 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 hidden or 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 hidden or 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 hidden or 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 hidden or 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
Oops, something went wrong.
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.
The
new_debitvector is sorted in ascending order by output value. For a branch-and-bound algorithm likeiter_search_for_matching_inputs, sorting inputs in descending order of value can often lead to faster convergence by pruning branches earlier. Sincestd::cmp::Reverseis imported but not used, consider sorting in reverse order to potentially improve performance. Ifiter_search_for_matching_inputsis not on a critical path and is used infrequently, this optimization could be deferred as per repository guidelines on performance trade-offs.References
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.
@gemini-code-assist
because we want search for explicit matches, if we sort the branch ascending order, when we get to the actual search algorhtim, we can do this:
there by pruning the branch.
If we do decending order, we cannot do this and we have to finish searching that entire 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.
You make a very good point. My suggestion was based on a general heuristic for branch-and-bound algorithms, where sorting in descending order can often lead to faster convergence by finding a solution quicker or pruning branches that quickly exceed the target. However, for your specific implementation, where you are looking for an exact match and have the pruning condition
if new_total > amount_sent { return false; }, sorting the inputs in ascending order is indeed more effective. This allows you to prune branches as soon as the sum exceedsamount_sent, knowing that any subsequent (larger) inputs would also exceed the target. Thank you for clarifying the specific logic ofiter_search_for_matching_inputs.