Implement AST parent edges

[maximiliankaul]

WIP!

• Python
• C++
• Java
• Go
• Converting LLVM frontend towithChildren style #1621
• Typescript
• Passes
• @oxisto this in nested blocks is not an ASTStackProvider
• Performance evaluation? (@oxisto +1% for go tests)
• Documentation
• AST parent is labeled "AST" in neo4j -> remove from neo4j

[KuechA]

I guess this PR is obsoleted by #1646 and #1642 and should be closed?

[maximiliankaul]

I guess this PR is obsoleted by #1646 and #1642 and should be closed?

No, we want to include this work once the withChildren { ... } (or similar) stuff is merged into main.

[oxisto]

I propose to close this in favour of the eventual node build v2 (#1874)

[maximiliankaul]

I propose to close this in favour of the eventual node build v2 (#1874)

I'm ok with closing this, if the new nodebuilder supports the idea withChildren { ... } (name open to debate) from this PR. Can you please give some example code how the front-end code is supposed to look like with the new nodebuilder?

[oxisto]

I propose to close this in favour of the eventual node build v2 (#1874)

I'm ok with closing this, if the new nodebuilder supports the idea withChildren { ... } (name open to debate) from this PR. Can you please give some example code how the front-end code is supposed to look like with the new nodebuilder?

Still open to discussion but the last state implements something like this:

example with scope:

var func = functionDeclaration(name = parseName("my::name"), rawNode = funcy).withScope {
  parameters += handle(funcy.argsy)
}

and without scope

var func = functionDeclaration(name = parseName("my::name"), rawNode = funcy) {
  parameters += handle(funcy.argsy)
}