Tsoding livestreams trying out C3 (programming language) [video]
youtube.com
youtube.com
And a LSP exists, but isn't the most stable: https://github.com/pherrymason/c3-lsp
Well, maybe the last bit isn't true for webdev, where if the code rots it's simply being deleted. Web applications, if they're taken off production, they're nowhere to be seen, most people never realizing they ever existed, but even if they knew those applications existed at some point in time, they would never be able to even see how they looked like.
And you wouldn't believe what happened next!
But seriously: what results?
> Rationale: It is very difficult to make goto work well with defer and implicit unwrapping of optional results. It is not just making the compiler harder to write, but the code is harder to understand as well.
That seems to fit your heuristic. Goto being difficult to implement in the compiler doesn't match expected reality.
So seeing someone say that their compiler struggles to represent goto throws some doubt on how the thing is implemented. Goto should generally be the easiest possible control flow to translate into your IR.
And you might say "so what, the compiler can be complicated, just make the language easy to use". However, one design constraint is to not make the language hard to reimplement.
And you might not agree with that constraint, but some people feel that this is indeed important. Important enough to not include `goto` as long as the use cases of `goto` are all covered.