summaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAgeFilesLines
* Disabled failing build manager tests.Martin Odersky2012-09-206-1/+1
| | | | | | | | | | | | | | | | | | | | | | When the refined build manager computes its change sets it mixes up the types. It computes constructors of inner classes of the first compilation that point to types of the second compilation. This breaks a useful assertion in ExtensionMethods. The error you get for t4245 is java.lang.AssertionError: assertion failed: unexpected constructor erasure A#6956.this.B#20211 for class B#6963 What goes on here is that the primary constructor of inner class B#6963 points to the new version of that inner class A#6956.this.B#20211. This happens during the computation of change sets, not during normal compilation. Since it looks like the computation of change sets is broken I have disabled the tests, rather than disabling the assertion. It seems that during residential compilation, the result type of a constructor can be a different version of the enclosing class. I could not reproduce this
* New test case for SI-6337Martin Odersky2012-09-201-0/+16
| | | | | This test case shows that the variant in the comment of SI-6337 now compiles also.
* New test case for closing SI-6385Martin Odersky2012-09-202-0/+20
| | | | | The fixes for SI-6260 + elimination of hlaf-boxing also solve SI-6385
* Value classes: eliminated half-boxingMartin Odersky2012-09-206-4/+66
| | | | | | | We now apply erasure of value classes everywhere. previously, erasure was disabled in the value class itself. This led to irregegularities and bugs. See test run/valueclasses-pavlov.scala for something that led to a ClassCastException before.
* Fixes SI-6260Martin Odersky2012-09-204-0/+43
| | | | | | | | Guards against bridge methods that clash with other methods. Two tests: The neg test is the original ticket. The run test tweaks things slightly so that the generated bridge method does not clash, and tests that the necessary unboxings are indeed performed at runtime.
* Merge pull request #1331 from scalamacros/ticket/5943Grzegorz Kossakowski2012-09-206-0/+40
|\ | | | | SI-5943 toolboxes now autoimport Predef and scala
| * SI-5943 toolboxes now autoimport Predef and scalaEugene Burmako2012-09-206-0/+40
| | | | | | | | | | | | | | | | | | | | Previously tb.typeCheck used default typer, which builds upon NoContext. Changing the context to analyzer.rootContext(NoCompilationUnit, EmptyTree) fixed the missing imports problem. Unfortunately this doesn't help in cases like "math.sqrt(4.0)" because of https://issues.scala-lang.org/browse/SI-6393. But anyways I'm adding this test case to pending.
* | Merge pull request #1338 from scalamacros/ticket/5418Grzegorz Kossakowski2012-09-204-0/+17
|\ \ | | | | | | existentially typed macro expansions now work fine
| * | test case closes SI-5418Eugene Burmako2012-09-182-0/+13
| | | | | | | | | | | | | | | | | | Now, when the existential reification bug is fixed, I've been able to take a look at SI-5418, and, apparently, the problem with importers has fixed itself during these 9 months of the bug being active.
| * | existentially typed expansions now work fineEugene Burmako2012-09-182-0/+4
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If one tries to compile the following code with the parent of this commit: ru.reify(new Object().getClass) then the following error will occur: Test.scala:2: error: type mismatch; found : $u.Expr[Class[_ <: Object]] required: reflect.runtime.universe.Expr[Class[?0(in value <local Test>)]] where type ?0(in value <local Test>) <: Object ru.reify(new Object().getClass) ^ This happens because macro expansions are always typechecked against the return type of their macro definitions instantiated in the context of expandee. In this case the expected type contains skolems which are incompatible with wildcards in the type of the expansion. I tried all the incantations I could think of - without any success. Luckily I met Martin who pointed me at the same problem solved in adapt (see the diff w.r.t Typers.scala).
* | Merge pull request #1358 from scalamacros/ticket/6392Grzegorz Kossakowski2012-09-204-0/+20
|\ \ | | | | | | SI-6392 wraps non-terms before typecheck/eval
| * | SI-6392 wraps non-terms before typecheck/evalEugene Burmako2012-09-194-0/+20
| | | | | | | | | | | | | | | Wrap non-term arguments of typecheck and eval, so that toolboxes can work with full-fledged files (except for package declarations).
* | | Merge pull request #1354 from scalamacros/ticket/6363Eugene Burmako2012-09-1921-117/+139
|\ \ \ | |/ / |/| | merges scala.reflect.base into scala.reflect.api
| * | 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 #1204 from chuvoks/rbGrzegorz Kossakowski2012-09-191-0/+42
|\ \ \ | | | | | | | | Rank based take/drop/slice
| * | | Add RedBlackTree tests for take/drop/slice.Juha Heljoranta2012-09-181-0/+42
| | | | | | | | | | | | | | | | Addresses review feedback by axel22.
* | | | Merge pull request #1343 from namin/dynamic-sigGrzegorz Kossakowski2012-09-193-2/+74
|\ \ \ \ | |_|/ / |/| | | Fixes SI-6354: improved error messages for Dynamic signature mismatches.
| * | | Fixes SI-6354: improved error messages for Dynamic signature mismatches.amin2012-09-193-2/+74
| | | | | | | | | | | | | | | | | | | | | | | | If an error occurs afer a Dynamic rewriting, augment the error message with the rewritten tree and a hint to check the Dynamic method signature.
* | | | 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.