Design for d6tflow framework

[cqfn]

Design for d6tflow framework

[KatGarmash]

@lyriccoder can you please write this issue in terms of Problem and Proposed solution

Also, give the issue a more informative name

[lyriccoder]

Bonobo can run tasks in parallel (it is written, i can't check it).
Also, it can run child tasks automatically.

I didn't solve the issue with aggregation of results to global csv:

[KatGarmash]

@lyriccoder

Some comments:
(1) step find_EMS: do we need to extract AST at this stage? it's an expensive operation (i think) and it'd be nice to do it after filtering
(2) in the abstract representation of the dataflow, I'd merge filters into one "Filter", as we may modify the sequence of filters in the future
(3) in ur representation of dataflow, you write "prev filters": you don't actually pass filters, but some filtered items. can you specify them?

[lyriccoder]

1. Of course we need, how can we compare method declaration and method invocation and iterate over all methods?
   We can do it only with ast
2. I've done it since we can omit some filter, if we merge them we wont; be able to discard them one by one
3. It's the previous results, you are right. It has previous results and plus one filter.

E.g., if we filter by ncss, we add to the all data ncss value. If we filter invocations by the SINGLE_STATEMENT_IN_IF filter, we add it to the final result

[KatGarmash]

(1) OK. do we need to pass the AST to the next step then?

(2) I meant, just have a more abstract representation processing steps. Merging them is a way of abstraction

(3) Filter is not data, it s an operator. Or do you mean something else by "filter"? The edges have to be labeled with data only. Nodes are operators. You can maybe write "filters(data)"

[lyriccoder]

1. we need full ast for inlining
2. --
3. I need to replace the word filter with data