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, 4 insertions, 4 deletions

diff --git a/test/files/pos/javaReadsSigs/fromjava.java b/test/files/pos/javaReadsSigs/fromjava.java
index eca63961d5..92441b0c6b 100644
--- a/test/files/pos/javaReadsSigs/fromjava.java
+++ b/test/files/pos/javaReadsSigs/fromjava.java
@@ -22,11 +22,11 @@ class B { };
 class Contra {
   // Not an Ordering<Character>.
   static Ordering<Object> charOrd = scala.math.Ordering.Char$.MODULE$;
-  
+
   public boolean useCharOrd() {
     return charOrd.compare(new Object(), new Object()) == 0;
   }
-  
+
   static Numeric<?> intNum = scala.math.Numeric.IntIsIntegral$.MODULE$;
 }
 
@@ -36,13 +36,13 @@ public class fromjava {
       return null;
     }
   };
-  
+
   public static Function1<Tuple2<? extends Object, B>, B> f2 = new scala.runtime.AbstractFunction1<Tuple2<? extends Object, B>, B>() {
     public B apply(Tuple2<? extends Object, B> tup) {
       return tup._2();
     }
   };
-  
+
   public static String vector(Vector<String> x) {
     Vector<String> y = x.take(2);
     return y.head();