Revised restrictions for value classes and unversal traits

and brought compiler in line with them. One thing we can accept IMO are nested
classes (nested objects are still a problem). In fact, it makes no sense to
exclude nested classes from value classes but not from universal traits. A class
nested in universal trait will becomes a class nested in a value class by
inheritance. Note that the reflection library already contains a universal trait
with a nested class (IndexedSeqLike), so we should accept them if we can.

1 files changed, 4 insertions, 12 deletions

diff --git a/test/files/neg/t5882.check b/test/files/neg/t5882.check
index df01c7bc0a..b9ca5a1b2a 100644
--- a/test/files/neg/t5882.check
+++ b/test/files/neg/t5882.check
@@ -1,15 +1,7 @@
-t5882.scala:2: warning: case classes without a parameter list have been deprecated;
-use either case objects or case classes with `()' as parameter list.
-  case class Scope
-                  ^
-t5882.scala:2: error: value class may not have nested class definitions
-  case class Scope
+t5882.scala:4: error: nested object is not allowed in value class
+  case class Scope()
              ^
-t5882.scala:3: error: value class may not have nested class definitions
-  class Foo
-        ^
-t5882.scala:4: error: value class may not have nested module definitions
+t5882.scala:5: error: nested object is not allowed in value class
   object Bar
          ^
-one warning found
-three errors found
+two errors found