Workaround for "package is not a value".

Not actually a fix, but when we see a package where a module is
expected, it's not a great stretch to try the package object.
References SI-5604.
Rename ConcurrentTrieMap to concurrent.TrieMap.

Introduced the collection.concurrent package and introduced the
concurrent.Map trait there. Deprecated the mutable.ConcurrentMap trait.

Pending work - introduce the appropriate changes to JavaConversions
and JavaConverters.
Merge remote-tracking branch 'axel22/feature/collection-concurrent' into develop
Merge remote-tracking branch 'jsuereth/remove-sbaz-update-man' into develop
String interpolation bug fix

This change fixes a bug in class StringContext.scala.
Parts were not correctly added to the resulting string.

This commit includes a test case which covers the
example reported in the bug.

Closes SI-5614.
Add JavaConversions and JavaConverters concurrent.Map support.

This required deprecating several old methods for converting ConcurrentMap.
Also, several new wrappers were introduced for concurrent.Map. Once we
remove ConcurrentMap in 2.11, we can remove its corresponding wrappers and
conversions in JavaConversions and JavaConverters.
SIP-11 String Interpolation Simplification

Changed StringContext.f which implements the formatted
string interpolator.

Any '%' not in formatting position is left in the resulting string literally.
However, instead of adding %s format holders and extending the args with "%"
expressions, these '%' are replaced by '%%'. The formatter then converts '%%'
(percent formatter) to the literal '%' (\u0025). This also simplifies the spec.

The interpolation tests still pass.
SIP-11 String Interpolation Simplification

Changed StringContext.f which implements the formatted string interpolator.

Any '%' not in formatting position is left in the resulting string literally.
However, instead of adding '%s' format holders and extending the args with
"%" expressions, these '%' are replaced by '%%'. The formatter then converts
'%%' (percent formatter) to the literal % (\u0025).

The interpolation tests still pass.
Work on source compatibility between akka and scala futures.

Removed some methods from execution contexts.
Changed Awaitable interface.
Revived the lisp test.

All hail the lisp test!

Closes SI-4579.
Never write final fields outside of constructors.

Closes SI-3569, SI-3770.

Also threw in experimental -Yoverride-vars.  It's not robust.
Revert the lisp test.

The lisp test enjoys the suffering of others.
Add methods in the Future companion object.
Add withFilter and mapTo to futures.
Adds links to parallel collections overview in API docs

Now that there's an extensive parallel collections overview on http://docs.scala-lang.org, API comments should link to it ("see also" field). This commit also fixes a couple of broken links on some sequential collection types.
A couple tests for pending.
Cleaning up logging in specialization.
a fast, functional PartialFunction implementation

runtime.AbstractPartialFunction provides a default implementation
for the new-style partial function. In principle this class is only
subclassed by compiler-generated partial functions arising from matches.

Either
 - the apply method (old-style partialfun) or
 - the applyOrElse method (current scheme)
must be overridden, and the isDefinedAt method implemented.
The applyOrElse method implementation is provided to ease the
transition from the old scheme, since starr still generates
old-style PartialFunctions, but locker's library has the
new AbstractPartialFunction.

Thus, this implementation is intended as a drop-in replacement for the
old partial function, and does not require changes to the compiler.
(compiler patches, both for old and new-style pattern matching, follow)

- runtime.AbstractPartialFunction is based on PartialFunction.WithDefault
Original version of FunctionWithDefault by Odersky
(http://article.gmane.org/gmane.comp.lang.scala.internals/4032)
- better performance for OrElse#applyOrElse, OrElse#lift, PF.cond
- new combinator methods: PF#run, PF#runWith, PF.apply

authored by @pavelpavlov, refactored by @adriaanm, review by @paulp
old patmat support for the applyOrElse partial fun

minimal fixes for typedMatchAnonFun so it compiles

TODO: support for AbstractTotalFunction (when match is exhaustive)
virtpatmat support for the new partialfunction

avoid casting default call in applyOrElse:
the result type of the match is always B1,
not the result type inferred from typing the cases