Cull extraneous whitespace.

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.

1 files changed, 10 insertions, 10 deletions

diff --git a/test/files/run/t5857.scala b/test/files/run/t5857.scala
index bf67bedf54..c82fd88c08 100644
--- a/test/files/run/t5857.scala
+++ b/test/files/run/t5857.scala
@@ -2,44 +2,44 @@
 
 
 object Test {
-  
+
   def time[U](b: =>U): Long = {
     val start = System.currentTimeMillis
     b
     val end = System.currentTimeMillis
-    
+
     end - start
   }
-  
+
   def main(args: Array[String]) {
     val sz = 1000000000
-    
+
     val range = 1 to sz
     check { assert(range.min == 1, range.min) }
     check { assert(range.max == sz, range.max) }
-    
+
     val descending = sz to 1 by -1
     check { assert(descending.min == 1) }
     check { assert(descending.max == sz) }
-    
+
     val numeric = 1.0 to sz.toDouble by 1
     check { assert(numeric.min == 1.0) }
     check { assert(numeric.max == sz.toDouble) }
-    
+
     val numdesc = sz.toDouble to 1.0 by -1
     check { assert(numdesc.min == 1.0) }
     check { assert(numdesc.max == sz.toDouble) }
   }
-  
+
   def check[U](b: =>U) {
     val exectime = time {
       b
     }
-    
+
     // whatever it is, it should be less than, say, 250ms
     // if `max` involves traversal, it takes over 5 seconds on a 3.2GHz i7 CPU
     //println(exectime)
     assert(exectime < 250, exectime)
   }
-  
+
 }