Skip to content
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

Add GraphSearcher::resume #185

Merged
merged 5 commits into from
Jan 10, 2024
Merged

Add GraphSearcher::resume #185

merged 5 commits into from
Jan 10, 2024

Conversation

jbellis
Copy link
Owner

@jbellis jbellis commented Jan 10, 2024

No description provided.

@jbellis jbellis requested a review from jkni January 10, 2024 20:47
@jkni
Copy link
Collaborator

jkni commented Jan 10, 2024

I'm excited to have this available! This looks functionally correct, and I like the general structure. I wonder if it would make sense to separate the two functionalities of a node being a candidate (potentially becoming a result, making neighbors candidates) because roundtripping the evictedResults through candidates seems to do wasted work in fetching the neighbors iterator (since all neighbors are already visited).

EDIT: I'm actually not sure if this helps, depending on how the evictedResults compare to the current state of the candidates queue.

@jbellis
Copy link
Owner Author

jbellis commented Jan 10, 2024

Good point, how about this?

@jkni
Copy link
Collaborator

jkni commented Jan 10, 2024

LGTM.

@jbellis jbellis merged commit ac39af1 into main Jan 10, 2024
4 checks passed
@jbellis jbellis deleted the resume-2 branch February 28, 2024 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants