summaryrefslogtreecommitdiff
path: root/test/files/run/bug4279.scala
Commit message (Collapse)AuthorAgeFilesLines
* And so my attempt to have a performance test dr...Paul Phillips2011-03-291-38/+0
| | | | | | And so my attempt to have a performance test draws the final curtain, no review.
* I guess windows can show a < 500x difference an...Paul Phillips2011-03-251-2/+2
| | | | | | | | | I guess windows can show a < 500x difference and still give us confidence there isn't a 100,000x difference. Testing situation continues to confound and amaze. Trying to make 4279 not fail on windows, one more time and I will delete it and burn the bodies. No review.
* One hundred! One hundred times slower on window...Paul Phillips2011-03-211-1/+1
| | | | | | One hundred! One hundred times slower on windows! Ah, ha, ha! Adjusted test case, no review.
* Raised the threshold for the test looking at vi...Paul Phillips2011-03-141-2/+2
| | | | | | | | Raised the threshold for the test looking at view performance. I guess if views are only 50x as slow on windows that's still a lot better than 100,000. (The real issue is more like "it's windows" plus "it's windows running on virtualbox".) No review.
* A patch for views. Most relevant change:Paul Phillips2011-03-111-0/+38
Almost all view classes now list parents like trait Appended[B >: A] extends super.Appended[B] with Transformed[B] instead of the former trait Appended[B >: A] extends Transformed[B] with super.Appended[B] because as it was, the implementation of foreach in TraversableViewLike#Transformed was repeatedly trumping overrides found in e.g. IterableLike. This change was not without its own consequences, and much of the rest of the patch is dealing with that. A more general issue is clearly revealed here: there is no straightforward way to deal with trait composition and overrides when some methods should prefer B over A and some the reverse. (It's more like A through Z in this case.) That closes #4279, with some views being five orders of magnitude slower than necessary. There is a test that confirms they'll stay performance neighbors. In the view classes (Zipped, Mapped, etc.) I attended to them with comb and brush until they were reasonably consistent. I only use "override" where necessary and throw in some "final" in the interests of trying to anchor the composition outcome. I also switched the newSliced, newZipped, etc. methods to use early init syntax since a number have abstract vals and I found at least one bug originating with uninitialized access. There was a piece of a parallel collections scalacheck test failing, which I disabled out of expedience - am emailing prokopec. There is plenty of work left to do but paulp must get back to other 2.9 issues. This is the Zurich->SF airplane patch. No review.