hasLoop() seems to be a misleading name in that the user may think that it checks if the SCC contains a loop that satisfies
the criteria of the loop terminology (i.e. a normal loop).
Details
Diff Detail
Event Timeline
While i certainly agree that it's kinda confusing, i'm not really sure this is conceptually correct change.
https://en.wikipedia.org/wiki/Loop_(graph_theory)
In graph theory, a loop (also called a self-loop or a "buckle") is an edge that connects a vertex to itself. A simple graph contains no loops.
which is exactly the case here.
https://en.wikipedia.org/wiki/Cycle_(graph_theory)
seems more generic than that.
Yes, I agree, but it was the closest word I could find that is not "loop" but still gets the point across. I mean technically maybe the better term would be "hasALoopButNotNecessarilyANormalLoop()" but well... :P
In any case, that was an experience of mine as a newcomer. If you think it's not worth it, so be it. :)
llvm/tools/opt/PrintSCC.cpp | ||
---|---|---|
82–83 | Maybe we can keep the "Has self-loop here". |
llvm/tools/opt/PrintSCC.cpp | ||
---|---|---|
82–83 | Then this would look good to me |
llvm/tools/opt/PrintSCC.cpp | ||
---|---|---|
82–83 | Ok, uploading new diff in a bit. |
I'd be happy to help fix that problem. Please take a look at the llvm developer policy. :-)
I committed that (https://reviews.llvm.org/rG21390eab4c05e0ed7e7d13ada9e85f62b87ea484) but as it seems, I should have added the differential division in the commit message. I'll try the next commit to be better.
If that happens, this Phabricator review does not close automatically. It has to be closed manually using the "Add Action..." dropdown.
If that happens, this Phabricator review does not close automatically. It has to be closed manually using the "Add Action..." dropdown.
Noted.
err, i was specifically talking about this