Hello, Predef!

Predef could use some love. I noticed Predef.Tuple only defines
overloads up to arity 9, but then I saw that I could input up to 22
elements and still get a result. How do you like this:

scala> Tuple(1,2,3,4,5,6,7,8,9).getClass
res0: java.lang.Class[_] = class scala.Tuple9

scala> Tuple(1,2,3,4,5,6,7,8,9,10).getClass
res1: java.lang.Class[_] = class scala.Tuple1

Up until 9 a TupleN is created, and then at 10 it decides that since
there is no such 10-arg version you must have meant to call the 1-arg
version with a 10-tuple. Funny stuff. Either Predef needs to go to 22
or not try at all.

Can the 18-month deprecated lower case primitive aliases be removed, and
the Integer/Character aliases?

I am realllly skeptical of the need to have a bunch of methods from
Console aliased in Predef. If we could at least deprecate the read*
methods, we could reclaim the global namespace one at a time.

Is there some technical constraint that causes many things to be in the
scala package object, but some others (Map, Set, etc.) to be in Predef?
Seems like the package object is the best way forward, where that can't
be done perhaps an explanatory comment.

Do we need val $scope = scala.xml.TopScope?

Can these commented out bits go? And scala.runtime.StreamCons, which is
not used except from the below commented-out method?

- /** any array projection can be automatically converted into an array */
- //implicit def forceArrayProjection[A](x: Array.Projection[A]): Array[A] = x.force !!! re-enable?
-
- //implicit def lazyStreamToConsable[A](xs: => Stream[A]) = new runtime.StreamCons(xs)