Migrating Ast Node

• structs should not use inclusion on interfaces
• DON'T GO AROUND CHANGING THE TYPES OF THE STRUCT FIELDS TO BE INTERFACES
  • This would mean you may need to fix some of the getters and setters. Getters may need to return pointers or create new collections. Setters may need to add type assertions
• Struct fields should not hold struct values instead they should hold pointers to structs to match java.
  • Slices and other collections should have structs instead of pointers to structs

Adding interfaces

Sometimes the interface we are asserting may not have been defined already in that case.

• Find the corresponding the java interface and manually migrate that to the same file as you have the assertion.
• When migrating interfaces make sure all the parameters and return values are them self interfaces (This way you can turn generic methods to non-generic in go)
• If it is a simple marker interface adding a type alias is enough. Fallow the coding style in the file you are copying content to.
• Interface must have all the same methods as the original and must have the same name

Determining the go file to put source code

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

• When migrating interfaces and structs they must use the same name as the go source.