Elliott Stoneham

The compromise approach, if not all Haxe or all Go, would be for this project to use and maintain a public Haxe co-routine library, then extend that with a threaded...

You are right @TheTechsTech, I have glossed over the subject, the state that [goto.go](https://github.com/go2hx/go2hx/blob/3b321146cd1f02fc925dbbde1cc1684063ce8434/analysis/goto.go#L18) does currently capture are the local variables (which need to go inside the call-frame on a...

I notice that both [nadako/haxe-coroutines](https://github.com/nadako/haxe-coroutines?tab=readme-ov-file#other-computation-abstractions) (that forms the basis of the Haxe compiler coroutine development branch), and [RealyUniqueName/Coro](https://github.com/RealyUniqueName/Coro) generate code that uses the same underlying "State Machine per coroutine function"...

These are wise words @TheTechsTech, thank you. If the project cannot find a suitable pure-Haxe approach to goroutines, I will certainly asist the project to simulate goroutines in the TARDISgo...

Like you, @neimanpinchas, I have been researching which Haxe "coroutine" libraries might be viable for use within go2hx. As you say, unfortunately [RealyUniqueName/Coro](https://github.com/RealyUniqueName/Coro) contains an Ocaml plugin, which is beyond...

In my ideal world @neimanpinchas , this project would create a coroutine library which allowed your [reflaxe_go](https://github.com/neimanpinchas/reflaxe_go) project to generate "go my_haxe_translated_to_go_fn()" from existing Haxe code.

For information, a go2hx branch has been created of [ohmrun/stx_coroutine](https://github.com/ohmrun/stx_coroutine/tree/go2hx), which certainly looks very interesting.

@neimanpinchas wrote above: > My approach would be to replace the sunspendable call flow with an array of OPS, then have a general purpose FORTH like vm, that would process...

Thank you for this @Yeaseen - you are correct, this aspect of Go has not yet been implemented within go2hx. It is a live issue for the project.