Joey
This is trickery then I first realized, this gives output ``2 0`` for both Haxe and Go: ```go package main type S struct{ p int } var test S func...
This can be simplified further to: ```go package main type myarr *[2]int func main() { var b myarr = nil a := any(b) _ = a } ``` It has...
How would a goroutine be created from the haxe side? Considering a goroutine for go needs to have the AST rewritten (in the same manner as goto) I appreciate you...
Great video on how to go from a simple Goroutine scheduler to the one Go uses: https://youtu.be/-K11rY57K7k?si=Zbr7tJFveIKPYnlZ
Nice document describing the runtime with mention of the Go scheduler: https://github.com/golang/go/blob/c386ed107e65f495acb6aacb0efcaade27da6a15/src/runtime/HACKING.md?plain=1#L6
Nadako's implementation is what the current PR for the Haxe compiler one is based off of. The others have been looked out but didn't fit for various reasons. The coroutine...
This is still an ongoing issue #261 point 2
It's improved quite a lost since last posting! So good news! Current commit: [3c48c83](https://github.com/go2hx/go2hx/commit/3c48c838a17bbb90b01bd7769f03507e04e574ce) Haxe: 3s Go: 15.519083ms Not sure why Haxe is not returning a floating point number worth...
For 2. making phantom variables to give the overload functions the type information needed seems to be the right choice.