summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* SI-6363 removes scala.reflect.baseEugene Burmako2012-09-1917-117/+121
| | | | | As the experience has shown, there's no need for a separate layer of reflection in scala-library.jar. Therefore I'm putting an end to it.
* fixes NameTypes in base namesEugene Burmako2012-09-194-0/+18
| | | | | | | | | | | | NameType is introduced in base.StandardNames#NamesBase to abstract away the difference between term names and type names in order to encode common names such as EMPTY or WILDCARD. Flavor-specific name repositories, such as TermNames and TypeNames are supposed to override NameType fixing it to correspondingly TermName or TypeName. Unfortunately I completely overlooked this and as a result some standard names were typed with insufficient precision, e.g. This(tpnme.EMPTY) didn't work.
* Merge pull request #1327 from scalamacros/ticket/6287Grzegorz Kossakowski2012-09-194-0/+49
|\ | | | | SI-6287 fixes synthetic symbol clashes in toolbox
| * test case closes SI-5770Eugene Burmako2012-09-182-0/+35
| |
| * SI-6287 fixes synthetic symbol clashes in toolboxEugene Burmako2012-09-172-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Apparently synthetic classes like $anonfun$1 have two properties: 1) Their names are generated using a counter unique to a compilation unit 2) After flatten they levitate to the nearest enclosing package As a result if we use an empty package to wrap toolbox codegen, then this package will soon be overflown by $anonfun$1 symbols, because: 1) New codegen session = new compilation unit = new counter which starts at 0 2) New codegen session = new anon funs that end up as children of empty package Creating a freshly named package for each codegen session fixed the problem. Now anonfuns from different sessions end up with different parents.
* | Merge pull request #1324 from scalamacros/ticket/6374Eugene Burmako2012-09-186-42/+17
|\ \ | | | | | | Scala reflection now supports Java CRTP
| * | refactors java reflection testsEugene Burmako2012-09-177-88/+16
| | | | | | | | | | | | All javac-produced artifacts are now placed into test/files/lib
| * | SI-6374 Reflection now works for anns with enum fieldsEugene Burmako2012-09-172-2/+2
| | | | | | | | | | | | | | | Enum members are static and, therefore, they need to be looked up in classSymbol(<enum>).companionModule, rather than in classSymbol(<enum>).
| * | Reflection no longer produces faux existentialsEugene Burmako2012-09-172-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | Because of using plain ExistentialType factory of a case class typeToScala sometimes returned existentials with empty quantifieds. Changing ExistentialType to newExistentialType, which simply returns the underlying types if params are empty, fixed the problem.
| * | SI-6374 Scala reflection now supports Java CRTPEugene Burmako2012-09-173-0/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Translation of Java types to Scala types has previously been existentionalizing raw types of ParameterizedType arguments. As shown in https://issues.scala-lang.org/browse/SI-6374 this leads to cyclic reference errors. If you wonder about the mechanism of the error, take a look at the comments to the aforementioned issue - there's a detailed explanation. However calling rawToExistential is completely unnecessary, because existential parameters of the results are immediately discarded, and only prefix and symbol are used later on (which means that existential extrapolation performed by rawToExistential also doesn't after the result). Finding out this was tough, but the rest was a piece of cake. Getting rid of the call to rawToExistential when translating ParameterizedType fixed the problem.
* | | Merge pull request #1298 from pavelpavlov/SI-5767Josh Suereth2012-09-1810-5/+109
|\ \ \ | | | | | | | | SI-5767 fix + protecting public FlatHashMap API
| * | | pull request feedbackPavel Pavlov2012-09-1810-5/+109
| | | |
* | | | Merge pull request #1340 from gkossakowski/revert-static-annotationGrzegorz Kossakowski2012-09-1812-451/+0
|\ \ \ \ | | | | | | | | | | Revert `@static` annotation
| * | | | Revert "Implement @static annotation on singleton object fields."Grzegorz Kossakowski2012-09-173-248/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 892ee3df93a10ffe24fb11b37ad7c3a9cb93d5de with exception of keeping `@static` annotation in the library so we can deploy a new starr that does not depend on it before removing it completely. Conflicts: src/compiler/scala/tools/nsc/backend/icode/GenICode.scala src/compiler/scala/tools/nsc/backend/jvm/GenJVM.scala src/compiler/scala/tools/nsc/transform/CleanUp.scala
| * | | | Revert "WIP add private/lazy checks and a few tests."Grzegorz Kossakowski2012-09-173-62/+1
| | | | | | | | | | | | | | | | | | | | This reverts commit 227239018b38ab7218ee6b30493c9c8e1836c8c9.
| * | | | Revert "Fixes SI-6189."Grzegorz Kossakowski2012-09-173-60/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 5a8dfad583b825158cf0abdae5d73a4a7f8cd997. Conflicts: src/compiler/scala/tools/nsc/backend/icode/GenICode.scala
| * | | | Revert "Fixes SI-6236."Grzegorz Kossakowski2012-09-174-32/+2
| | | | | | | | | | | | | | | | | | | | This reverts commit faa114e2fb6003031efa2cdd56a32a3c44aa71fb.
| * | | | Revert "Fix SI-4581."Grzegorz Kossakowski2012-09-175-42/+4
| | | | | | | | | | | | | | | | | | | | This reverts commit 373f22a2022519ab894c1ea77460e6460d7c2ee4.
| * | | | Revert "Fix SI-6294."Grzegorz Kossakowski2012-09-171-14/+0
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit cb393fcbe35d0a871f23189d791b44be1b826ed2. Conflicts: src/compiler/scala/tools/nsc/backend/icode/GenICode.scala
* | | | Merge pull request #1329 from scalamacros/ticket/5692Eugene Burmako2012-09-188-0/+28
|\ \ \ \ | | | | | | | | | | SI-5692 better error message
| * | | | SI-5692 better error messageEugene Burmako2012-09-188-0/+28
| |/ / / | | | | | | | | | | | | | | | | | | | | Doesn't fix the underlying issue with macros and type inference, but at least now the error message says exactly what needs to be done to make the error go away.
* / / / SI-5942 toolboxes now reset front endsEugene Burmako2012-09-182-0/+10
|/ / / | | | | | | | | | | | | FrontEnd => Reporter proxy now correctly redirects flush and reset back to the underlying front end.
* | | Merge pull request #1321 from namin/apply-dynamic-sugarGrzegorz Kossakowski2012-09-174-1/+29
|\ \ \ | | | | | | | | Fixed SI-6353: applyDynamic with sugared applications
| * | | Fixed SI-6353: applyDynamic with sugared applicationsamin2012-09-174-1/+29
| | |/ | |/| | | | | | | | | | | | | | | | - Accept sugared applications such as x(1) if x implements Dynamic, so x(1) gets re-written to x.apply(1). - When picking a dynamic rewrite for x.apply(1), favor applyDynamic instead of the default selectDynamic.
* | | Merge pull request #1320 from scalamacros/topic/is-implicitPaul Phillips2012-09-172-0/+17
|\ \ \ | | | | | | | | moves isImplicit from TermSymbol to Symbol
| * | | moves isImplicit from TermSymbol to SymbolEugene Burmako2012-09-162-0/+17
| | | | | | | | | | | | | | | | Because classes can also be implicit.
* | | | Merge pull request #1322 from paulp/topic/emptyArrayJosh Suereth2012-09-171-3/+3
|\ \ \ \ | | | | | | | | | | Topic/empty array
| * | | | Revert "Added constant empty array to the companion objects."Paul Phillips2012-09-161-3/+3
| | |/ / | |/| | | | | | | | | | This reverts most of commit 9d84e89d2 .
* | | | Merge pull request #1318 from odersky/ticket/6336Josh Suereth2012-09-172-0/+15
|\ \ \ \ | |/ / / |/| | | SI-6336 Disallows value types in structuralal refinements
| * | | SI-6336 Disallows value types in structuralal refinementsMartin Odersky2012-09-162-0/+15
| | | | | | | | | | | | | | | | | | | | Structural refinements already have a number of restrictions, e.g. cannot refer to type parameters of enclosing classes. We need to disallow value classes as well.
* | | | Merge pull request #1310 from scalamacros/ticket/6329Eugene Burmako2012-09-168-0/+59
|\ \ \ \ | |_|/ / |/| | | test suite for SI-6329
| * | | test suite for SI-6329Eugene Burmako2012-09-068-0/+59
| | | |
* | | | SI-6356 reflection now supports Java annotationsEugene Burmako2012-09-163-0/+43
| |/ / |/| | | | | | | | | | | Except for one thingie: java enums are currently not understood by Scala reflection, hence they aren't yet supported in annotations.
* | | Merge pull request #1302 from scalamacros/topic/reflectionEugene Burmako2012-09-1479-88/+88
|\ \ \ | | | | | | | | cleaning up reflection
| * | | SI-6342 cleans up toolbox APIEugene Burmako2012-09-1579-88/+88
| | | | | | | | | | | | | | | | | | | | | | | | 1) parseExpr => parse 2) runExpr => eval 3) Introduces compile(Tree): () => Any, since it has frequent uses
* | | | Merge pull request #1290 from retronym/ticket/no-implicit-to-anyrefPaul Phillips2012-09-142-0/+57
|\ \ \ \ | | | | | | | | | | A little cleanup along the Any to AnyRef trail.
| * | | | A little cleanup along the Any to AnyRef trail.Jason Zaugg2012-09-112-0/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Followup to 35316be and d3f879a. - Remove obsolete comments and replace them with a test. - Don't emit error addendum unless we know we're dealing with a value class.
* | | | | Merge pull request #1299 from namin/si-6245Paul Phillips2012-09-1411-4/+27
|\ \ \ \ \ | | | | | | | | | | | | Fix for SI-6245 with workaround for SI-2296.
| * | | | | Fix for SI-6245 with workaround for SI-2296.amin2012-09-1311-4/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | protected/super accessor issue: Don't subvert the creation of the standard protected accessor with the java interop accessor. For SI-2296, the compiler emits an error instead of causing an illegal access error at runtime.
* | | | | | Merge pull request #1304 from paulp/topic/empty-array-optimizationJosh Suereth2012-09-142-0/+11
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | Topic/empty array optimization
| * | | | | Added constant empty array to the companion objects.Paul Phillips2012-09-142-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Because there are lots of times when you just need an array and shouldn't have to allocate one every time or pick a random spot to cache yet another empty array.
* | | | | | Eliminate breaking relative names in source.Paul Phillips2012-09-143-35/+35
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These things are killing me. Constructions like package scala.foo.bar.baz import foo.Other DO NOT WORK in general. Such files are not really in the "scala" package, because it is not declared package scala package foo.bar.baz And there is a second problem: using a relative path name means compilation will fail in the presence of a directory of the same name, e.g. % mkdir reflect % scalac src/reflect/scala/reflect/internal/util/Position.scala src/reflect/scala/reflect/internal/util/Position.scala:9: error: object ClassTag is not a member of package reflect import reflect.ClassTag ^ src/reflect/scala/reflect/internal/util/Position.scala:10: error: object base is not a member of package reflect import reflect.base.Attachments ^ As a rule, do not use relative package paths unless you have explicitly imported the path to which you think you are relative. Better yet, don't use them at all. Unfortunately they mostly work because scala variously thinks everything scala.* is in the scala package and/or because you usually aren't bootstrapping and it falls through to an existing version of the class already on the classpath. Making the paths explicit is not a complete solution - in particular, we remain enormously vulnerable to any directory or package called "scala" which isn't ours - but it greatly limts the severity of the problem.
* | | | | Merge pull request #1271 from retronym/ticket/6331Josh Suereth2012-09-144-0/+144
|\ \ \ \ \ | | | | | | | | | | | | SI-6331 deconst If type / refine equality of floating point Constant types.
| * | | | | Test for consistency of Constant#{equals, hashCode}.Jason Zaugg2012-09-091-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For the examples I've constructed, they are consistent, but I put this down to good luck, rather than good management. The next commit will address this.
| * | | | | Refine equality of Constant types over floating point values.Jason Zaugg2012-09-082-0/+86
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The constant types for 0d and -0d should not be equal. This is implemented by checking equality of the result of doubleToRawLongBits / floatToRawIntBits, which also correctly considers two NaNs of the same flavour to be equal. Followup to SI-6331.
| * | | | | SI-6331 Avoid typing an If tree with a constant type.Jason Zaugg2012-09-082-0/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The fast path in typedIf added in 8552740b avoided lubbing the if/else branch types if they are identical, but this fails to deconst the type. This could lead to the entire if expression being replaced by a constant. Also introduces a new tool in partest for nicer checkfiles. // in Test.scala trace(if (t) -0d else 0d) // in Test.check trace> if (Test.this.t) -0.0 else 0.0 res: Double = -0.0
* | | | | | Merge pull request #1281 from jsuereth/fix/SI-4813Josh Suereth2012-09-141-0/+37
|\ \ \ \ \ \ | | | | | | | | | | | | | | Fix SI-4813 - Clone doesn't work on LinkedList.
| * | | | | | Fix SI-4813 - Clone doesn't work on LinkedList.Josh Suereth2012-09-141-0/+37
| | |/ / / / | |/| | | | | | | | | | | | | | | | | | | | | | * Added extensive test for clone across all standard mutable collections * Fixed clone implementations when needed so they work.
* | | | | | Merge pull request #1295 from scalamacros/ticket/6323Eugene Burmako2012-09-1471-166/+223
|\ \ \ \ \ \ | | | | | | | | | | | | | | improvements for type tags
| * | | | | | SI-6310 AbsTypeTag => WeakTypeTagEugene Burmako2012-09-1463-148/+148
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The new name for AbsTypeTag was a matter of a lengthy discussion: http://groups.google.com/group/scala-internals/browse_thread/thread/fb2007e61b505c4d I couldn't decide until having fixed SI-6323 today, which is about trying to reflect against a local class using typeOf. The problem with local classes is that they aren't pickled, so their metadata isn't preserved between Scala compilation runs. Sure, we can restore some of that metadata with Java reflection, but you get the idea. Before today typeOf of a local class created a free type, a synthetic symbol, with a bunch of synthetic children that remember the metadata, effectively creating a mini symbol table. That might be useful at time, but the problem is that this free type cannot be reflected, because the global symbol table of Scala reflection doesn't know about its mini symbol table. And then it struck me. It's not the presence of abs types (type parameters and abs type members) that differentiates arbitrary type tags from good type tags. It's the presence of types that don't map well on the runtime world - ones that can't be used to instantiate values, ones that can't be reflected. So we just need a name for these types. Phantom types are compile-time only concept, whereas our types can have partial correspondence with the runtime. "Weak types" sound more or less okish, so let's try them out.