summaryrefslogtreecommitdiff
path: root/test/files/run/typetags_without_scala_reflect_manifest_lookup.scala
Commit message (Collapse)AuthorAgeFilesLines
* hardens DirectTest against missing -d settingsEugene Burmako2012-09-261-1/+1
| | | | | And also explicitly specifies -d in a test where I forgot to do that. Double checking never hurts.
* don't try to create tags w/o scala-reflect.jarEugene Burmako2012-09-201-0/+29
Since recently type tags have relocated to scala-reflect.jar, meaning that they are no longer always on library classpath. In the compiler we do have code that generates type tags, and this code is bound to fail if scala-reflect.jar isn't there. I though this wouldn't be a problem, because type tag materialization is only going to be triggered by users explicitly requesting a type tag. That's generally true, but I overlooked a corner case. Since we provide manifest <-> type tag compatibility, manifest lookup can sometimes trigger tag lookup, which might result in tag synthesis, which blows up like this: http://groups.google.com/group/scala-internals/browse_thread/thread/166ce4b71b7c46bb This commit also ensures that type tag generation/interop doesnt sneak into the code of the libraries that don't have scala-reflect.jar on their classpath. For details refer to the discussion at scala-internals: http://groups.google.com/group/scala-internals/browse_thread/thread/72f6ce3010f4d8