summaryrefslogtreecommitdiff
path: root/test/files/pos/t2994a.scala
Commit message (Collapse)AuthorAgeFilesLines
* Cull extraneous whitespace.Paul Phillips2013-09-181-2/+2
| | | | | | | | | | | | | | | | | | | | | One last flurry with the broom before I leave you slobs to code in your own filth. Eliminated all the trailing whitespace I could manage, with special prejudice reserved for the test cases which depended on the preservation of trailing whitespace. Was reminded I cannot figure out how to eliminate the trailing space on the "scala> " prompt in repl transcripts. At least reduced the number of such empty prompts by trimming transcript code on the way in. Routed ConsoleReporter's "printMessage" through a trailing whitespace stripping method which might help futureproof against the future of whitespace diseases. Deleted the up-to-40 lines of trailing whitespace found in various library files. It seems like only yesterday we performed whitespace surgery on the whole repo. Clearly it doesn't stick very well. I suggest it would work better to enforce a few requirements on the way in.
* Revert "SI-7517 type constructors too eagerly normalized."Paul Phillips2013-06-031-3/+5
| | | | | | | | | This reverts commit 14534c693d2eb6acafaf8244c14b5643388fbd67. It turns out this approach was breaking the working variations in the submitted test case even as it was unbreaking the unworking one, but I never managed to uncomment them. Fortunately retronym's test case was not so lackadaisical.
* SI-7517 type constructors too eagerly normalized.Paul Phillips2013-05-311-5/+3
| | | | | | | | | | | | | | I think 403eadd0f1 was largely a symptomatic remedy (not that we shouldn't harden against such outcomes) and that this commit gets closer to the root causes. The unanticipated change to test/files/run/t6113.check is like a cry of support from the jury box. -Foo[[X](Int, X)] +Foo[AnyRef{type l[X] = (Int, X)}#l] We should continue to look at calls to normalize with grave suspicion.
* Begone t1737...Hubert Plociniczak2011-11-021-2/+2
|
* closes #2994Adriaan Moors2010-03-081-0/+27
make normalize slightly more aggressive in loading symbol info, while ) tolerating the righteous cycle (use sym.info.typeParameters instead ) of unsafeParams this is needed to make sure higher-kinded types have ) their type parameters (otherwise we'd get a PolyType with NoSymbol for ) typeParams )