Skip to content

Fix #2292: Do not crash when a top-level class is untyped #2352

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 2 commits into from
May 8, 2017

Conversation

smarter
Copy link
Member

@smarter smarter commented May 2, 2017

This can happen when the class is in a package that got an error type.

This can happen when the class is in a package that got an error type.
This is a more general fix than what the previous commit did.
Copy link
Contributor

@odersky odersky left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@odersky odersky merged commit 37255c5 into scala:master May 8, 2017
@allanrenucci allanrenucci deleted the fix/not-assigned-2 branch December 14, 2017 19:22
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