-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stack overflow in compiler on a cyclic import #760
Labels
Comments
The |
The What is relevant for this issue is that it is, indeed, just a stack overflow. :)
|
dvdvgt
pushed a commit
that referenced
this issue
Jan 15, 2025
Resolves the `Effect Compiler Crash: null` part of #760. The actual problem there was that `e.getMessage` can return `null` and it does for... _StackOverflowException_ 🥳. Looking at the docs, it's recommended to use `e.toString`. While I was at it, I modified stack trace printing, now we do it properly by using `.printStackTrace`. This is very related to #731, I just want to get this out quickly to unblock other problems.
dvdvgt
pushed a commit
that referenced
this issue
Jan 17, 2025
Resolves the `Effect Compiler Crash: null` part of #760. The actual problem there was that `e.getMessage` can return `null` and it does for... _StackOverflowException_ 🥳. Looking at the docs, it's recommended to use `e.toString`. While I was at it, I modified stack trace printing, now we do it properly by using `.printStackTrace`. This is very related to #731, I just want to get this out quickly to unblock other problems.
EveEme
pushed a commit
to EveEme/effekt
that referenced
this issue
Jan 20, 2025
Resolves the `Effect Compiler Crash: null` part of effekt-lang#760. The actual problem there was that `e.getMessage` can return `null` and it does for... _StackOverflowException_ 🥳. Looking at the docs, it's recommended to use `e.toString`. While I was at it, I modified stack trace printing, now we do it properly by using `.printStackTrace`. This is very related to effekt-lang#731, I just want to get this out quickly to unblock other problems.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cyclic imports make the compiler crash. It would be appropriate to detect cyclic imports and report them to the user in a nicer way :)
I consider this pretty low priority since it's somewhat obvious what the problem is from the crash.
(Reported by @TheDying0fLight)
a.effekt
b.effekt
crashes the compiler:
The text was updated successfully, but these errors were encountered: