You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm struggling to find a smaller reproduction, but I can confirm that changing FrameType.BadFrame to just FrameType.Bad makes the error disappear.
Changing it back to BadFrame immediately triggers the crash again.
nijolas
changed the title
Consistently reproducible LSP crash while working on code
Compiler crash when checking exhaustiveness against duplicate type constructors
Jun 13, 2024
Hello! Yes I think this is a bug introduced by our fault tolerant analysis, and the exhaustiveness checker failing to handle code that is invalid, while previously it would always be valid. I think it may be the same as the other issue.
Getting a compiler crash via the LSP consistently:
Here is the code file that's causing it:
I'm part way through working on the Bowling exercise on Exercism. As I was working, VSCode threw up an error saying:
And that's what I found in the output. I restarted VSCode a few times, and this code seems to be triggering it consistently.
This is not an issue for me of course! But I thought it might help toward improving tooling and compiler errors 🙏
The text was updated successfully, but these errors were encountered: