Migrate an ast node definition from java to go
When migrating an ast node definition start with the machine migrated code in ./ballerina-lang-go/ast/migrated.
There will be a go file corresponding to the java ast node already migrated. First copy the relevant content to the
corresponding go file. If the file you are migrating has dependency on some other ast node that haven't been migrated recursively migrate them as well.
YOU SHOULD ALWAYS FULLY MIGRATE A FILE IN migrated DIRECTORY not just parts you need. After migrating a file rename it from go_todo to go_done
var _ $Interface = &$Struct).Sometimes the interface we are asserting may not have been defined already in that case.
To determine the corresponding go file check what package it belongs to. For example if it belong to
org.wso2.ballerinalang.compiler.tree.bindingpatterns then it should end up in binding_patterns.go file.
Those in top org.wso2.ballerinalang.compiler.tree ends up in ast.go file