Skip to content

Add additional test case for #4661 #4950

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
Aug 15, 2018
Merged

Conversation

abeln
Copy link
Contributor

@abeln abeln commented Aug 15, 2018

The test case comes from #4660, which is a related bug.

@abeln abeln requested a review from liufengyun August 15, 2018 16:56
The test case comes from scala#4660, which is a related bug.
Copy link
Contributor

@Blaisorblade Blaisorblade left a comment

Choose a reason for hiding this comment

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

LGTM. But this doesn't quite fix #4660 since that issue asks for an actual explanation for the warnings, which is a much bigger task. Luckily, the PR as written won't auto-close that issue, so it's OK.

Copy link
Contributor

@liufengyun liufengyun left a comment

Choose a reason for hiding this comment

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

LGTM, thanks @abeln !

@liufengyun liufengyun merged commit 61cba97 into scala:master Aug 15, 2018
@abeln abeln deleted the unreachable2 branch August 15, 2018 18:50
@@ -0,0 +1,15 @@
class C {
Copy link
Contributor

Choose a reason for hiding this comment

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

The convention is to prefix the test file name by i. The tests starting with t are the ones that come from scalac IIRC

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.

4 participants