Seems like there is some cases where the Go compiler does not handle abstract/concrete functions very well, leading to some ambiguous selector when trying to go build...
It would probably help if the Go compiler followed the same strategy same the other compilers (merging fragments into the concrete things) instead of keeping all the fragments also in the generated code.
I'll try to make a simple test illustrating the problem.
Seems like there is some cases where the Go compiler does not handle abstract/concrete functions very well, leading to some
ambiguous selectorwhen trying togo build...It would probably help if the Go compiler followed the same strategy same the other compilers (merging fragments into the concrete things) instead of keeping all the fragments also in the generated code.
I'll try to make a simple test illustrating the problem.