-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Fix #7781: Avoid using nested package definition #7784
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
Conversation
Had to remove `sealed` from `Expr`
Had to remove `sealed` from `Type`
Now that Expr and Type are not sealed these do not need to be in the library
I think I have an alternative fix for that |
With #7786 this change should be no longer necessary. |
Reopened since we won't go ahead with #7786. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -0,0 +1 @@ | |||
2: Pattern Match Exhaustivity: _: Expr[Int] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is interesting, we don't have the warning before. I'll have a look at it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It made sense because Expr is not sealed anymore. The test case was clearly not exhaustive.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why the error was not there before
Had to remove
sealed
fromExpr
andType