Skip to content
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

Fix #4151: Report a somewhat helpful message for back-end exceptions. #4179

Merged
merged 1 commit into from Sep 7, 2020

Conversation

@sjrd
Copy link
Member

sjrd commented Sep 7, 2020

This implements exactly the same last resort mechanism as the JVM for back-end crashes. In particular, it applies for string literals that are too long to be serialized (in JVM bytecode or in SJSIR).

Arguably, this should be caught earlier as a nice front-end compile error, but that is not a job for Scala.js.

This implements exactly the same last resort mechanism as the JVM
for back-end crashes. In particular, it applies for string literals
that are too long to be serialized (in JVM bytecode or in SJSIR).

Arguably, this should be caught earlier as a nice front-end compile
error, but that is not a job for Scala.js.
@sjrd sjrd requested a review from gzm0 Sep 7, 2020
@gzm0
gzm0 approved these changes Sep 7, 2020
@gzm0 gzm0 merged commit bf86793 into scala-js:master Sep 7, 2020
2 checks passed
2 checks passed
check
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
Details
@sjrd sjrd deleted the sjrd:fix-crash-for-string-too-long branch Sep 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants
You can’t perform that action at this time.