Add test object-loses-type-alias-ok

dwijnand · dwijnand · commit 879a7f6eb8b7 · 2020-02-24T13:38:52.000Z
Type aliases can't be top-level (in the normal way, not in the Dotty way) because that type definition must live in some bytecode somewhere. So I wanted to check that that doesn't have any binary compatibility concerns if you lose the alias. (In truth I was double-checking scala/bug#11888 (comment)).
diff --git a/functional-tests/src/test/object-loses-type-alias-ok/app/App.scala b/functional-tests/src/test/object-loses-type-alias-ok/app/App.scala
@@ -0,0 +1,5 @@
+object App {
+  def main(args: Array[String]): Unit = {
+    println(A)
+  }
+}
diff --git a/functional-tests/src/test/object-loses-type-alias-ok/problems.txt b/functional-tests/src/test/object-loses-type-alias-ok/problems.txt
diff --git a/functional-tests/src/test/object-loses-type-alias-ok/v1/A.scala b/functional-tests/src/test/object-loses-type-alias-ok/v1/A.scala
@@ -0,0 +1,3 @@
+object A {
+  type Str = java.lang.String
+}
diff --git a/functional-tests/src/test/object-loses-type-alias-ok/v2/A.scala b/functional-tests/src/test/object-loses-type-alias-ok/v2/A.scala
@@ -0,0 +1 @@
+object A

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1,3 @@`
	`1`	`+object A {`
	`2`	`+ type Str = java.lang.String`
	`3`	`+}`