Make Kruskal spanning tree accept weight vector instead of matrix#486
Merged
Make Kruskal spanning tree accept weight vector instead of matrix#486
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #486 +/- ##
=======================================
Coverage 97.19% 97.19%
=======================================
Files 121 121
Lines 7105 7107 +2
=======================================
+ Hits 6906 6908 +2
Misses 199 199 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Krastanov
force-pushed
the
spanning-tree-from-vector
branch
from
7ee34e9 to
f053047
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Kruskal seems to be the only one in the current implementation that accepts a matrix and converts it to a vector.
Instead of this additional allocation, I refactored the two steps to be able to call the function with a weight vector directly, it was the form I needed in the first place for something in which I manipulate weight vectors