-
Notifications
You must be signed in to change notification settings - Fork 4
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
Manual graph transposition #107
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #107 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 10 10
Lines 778 806 +28
=========================================
+ Hits 778 806 +28 ☔ View full report in Codecov by Sentry. |
Benchmark Results
|
I am not a fan of reimplementing what's already in a standard library just to shave off one allocation (the new nzval, if I understand correctly). Are you sure there is no other way? |
I don't see another solution. |
@gdalle What is the command to apply the formater on the code? |
JuliaFormatter.format with a path, or just control shift I in VSCode. |
1de3fde
to
3d55430
Compare
Actually I wanted to work some more on this one, since the other PR is very short I'll take care of rebasing |
I don't really like this handwritten loop with obscure logic, even though you documented it well I still struggle to understand it. I opened #114 with a much more elegant 3-line implementation, which should still shave off all unneeded allocations but one (haven't benchmarked though). I suggest we merge that one and possibly revisit this afterwards. |
Also, some of the benchmarks show degradation but I think that's just because they're incredibly noisy. Will try to fix them |
If you propose, don't merge it! |
You're right, I'm sorry. I merged mine first because the benchmarks showed virtually no difference, but I should have waited for you to weigh in.
We obviously have diverging opinions on this, so let's judge from the benchmarks? I have merged
Precisely because it is so classic, my assumption is that there is a version of it in SparseArrays that is better than ours (both in terms of efficiency and reliability), so we should just reuse it instead of adding complexity to our code base. |
No description provided.