Skip to content

Commit 486f412

Browse files
committed
Delete ErrorMessageTest
I must say, these error message tests are probably the biggest productivity killer in working with dotty. Why do we have them? What do they accomplish? They certainly throw lost of spammers in the works.
1 parent 0ec4d98 commit 486f412

File tree

1 file changed

+0
-14
lines changed

1 file changed

+0
-14
lines changed

compiler/test/dotty/tools/dotc/reporting/ErrorMessagesTests.scala

Lines changed: 0 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -988,20 +988,6 @@ class ErrorMessagesTests extends ErrorMessagesTest {
988988
assertEquals(method.show, "method foo")
989989
}
990990

991-
@Test def expectedTypeBoundOrEquals =
992-
checkMessagesAfter(FrontEnd.name) {
993-
"""object typedef {
994-
| type asd > Seq
995-
|}
996-
""".stripMargin
997-
}.expect { (ictx, messages) =>
998-
implicit val ctx: Context = ictx
999-
1000-
assertMessageCount(1, messages)
1001-
val ExpectedTypeBoundOrEquals(found) :: Nil = messages
1002-
assertEquals(Tokens.IDENTIFIER, found)
1003-
}
1004-
1005991
@Test def classAndCompanionNameClash =
1006992
checkMessagesAfter(RefChecks.name) {
1007993
"""

0 commit comments

Comments
 (0)