Requests for clarifications & additional documentation

[Ellpeck]

This is a list of things I still struggle to understand and that, especially for other users of the API, should be documented better if possible. Some of these may already be documented and I just missed or misunderstood them.

• What are we meant to do when we feel we lack some (complex) fundamental piece of understanding about how flowR works? Is the original master's thesis still the place to get that information, since it appears to be so far removed from flowR's current architecture?
• Clearer link between the new dataflow docs (which are very good so far) and the typescript api. Specifically things like how to get related edges and nodes of specific types, for example: retrieving the condition/true/false branches of a node that represents an if call.
• I feel that some explanations in the dataflow doc have phrasing that is too complex. This may just be an issue with my personal understanding & lack of experience, but for example, when reading the sentence "The source vertex is usually a define variable that is defined by the respective target use", the following questions come up for me:
  • What's a "define variable" in this context?
  • What's a "target use"? Is this sentence even using "target use" as a noun like in my understanding of the phrasing?
• More info about control dependencies, like what all is marked as one and why.
• Sometimes I struggle to instinctually understand the meaning of an edge direction, especially for edge types like argument that don't imply directionality in their name (whereas "defined by", for example, is clearer because you can read it as "x is defined by ->").