NemoTR

This doesn't match the official documentation: 

Tried on version 1.1.891, still not fixed. 

I found another way to solve this problem, we can add a new type of node named "ARGUMENT", every argument of "CALL" node has its corresponding "ARGUMENT" node, This kind...

The two ways may need to make big changes, an easier way to solve this problem is to let "IDENTIFIER" node exist in DDG. In this case, just link (PARAM,...

> I think this is just an effect that is produced by the dot-plotting code, which aims to simplify the representation. In the underlying graph, we in fact create REACHING_DEF...

 So weired.  Are these output wrong? Why the outE's outVs of a node are the node itself?

The `outV` traversal seems broken.

Thanks for answering me. @mpollmeier So if there is an edge `a -> b` and I am at `a` now, I should use `a.outE.inV` to traverse to `b` , is...

> So if there is an edge `a -> b` and I am at `a` now, I should use `a.outE.inV` to traverse to `b` , is this right? This is...

Much appreciated! > but to go from `a->b` you typically just use `a.out`. I'll be looking forward to the fixing of `outV` traversal and simply use it in the above-mentioned...