Fix unknown compiler crash printing 'null' #780
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves the
Effect Compiler Crash: null
part of #760.The actual problem there was that
e.getMessage
can returnnull
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.