Haxe compiler server issues with macros

[zommerfelds]

Do you use vscode with the Haxe compilation server mode? I had a lot of ramp up issues when using Echoes because macro issues would often get the server into a permanent broken state.

Now I trained myself to restart the Haxe compilation server whenever I see huge cryptic compiler errors :)

Just wanted to point this out in case anyone searches for the this. It's probably an issue in Haxe, but hard to repro. But maybe there are things this repo could do to avoid falling into those issues.

Sorry that I don't have a repro case right now.

[player-03]

I get those too, occasionally. I think I've managed to fix some of them, but the fact that they're so rare makes them hard to track down.

[onehundredfeet]

These are really hard to fix with this ECS. I've fixed a few as well and try to stay on top of them when I add new things.

[player-03]

It's been a couple months since my last big macro rewrite, and I haven't seen the error at all. I think maybe it's fixed.

I've been seeing a new issue in its place, though. The completion server sometimes locks up when compile errors are detected. Not sure if this new one is Echoes-related at all, but it's every bit as annoying.

[NitroPlum]

I'm also seeing this. It seems like the smallest issue causes my language server to crash.

[player-03]

Not just me, then. Ok, I'll try to make time to work on this.

[player-03]

Ugh, this is proving difficult. I've opened an issue here in hopes that someone on the Haxe team knows what's going on.

[player-03]

I finally found a workaround!

I've only tested it on my computer, but it should work anywhere. Let me know if not.

[zommerfelds]

Thanks for the investigation, this looked tricky to debug!

…

On Fri, Jan 5, 2024, 04:13 player-03 ***@***.***> wrote: Closed #6 <#6> as completed. — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAJTYTTTYU3XDTRCY76ITBLYM5VWPAVCNFSM6AAAAAAT5B3TVCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGM4TOMRRGI4TQMQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[player-03]

Still haven't found the root of it, but I think that's for the Haxe devs to deal with. In the meantime, we have the workaround.