Skip to content

Improve diagnostics for bad Tasty files #3256

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

Merged
merged 1 commit into from
Oct 4, 2017

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Oct 4, 2017

  • always give absolute paths when reporting about bad class files
  • turn UnpickleException into a runtime error, so that additional
    file info is printed.

I used this change to figure out why launchIDE failed.

 - always give absolute paths when reporting about bad class files
 - turn UnpickleException into a runtime error, so that additional
   file info is printed.

I used this change to figure out why launchIDE failed.
@smarter smarter merged commit de7b370 into scala:master Oct 4, 2017
@allanrenucci allanrenucci deleted the change-unpickle-diag branch December 14, 2017 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants