Fix typo in documentation.
SI-7852 Test to show the status quo bytecode for "" == ...

Will be somewhat leaner after the next commit.
SI-7852 Omit null check for "".==

Although the same the code would be later optimized by -Yconst-opt,
we can offer the same lean byte code to those compiling without that
option by being more discerning when translating ==.

This helps people using bytecode based code coverage tools
such as jacoco that would emit "branch not covered" warnings
for the impossible null check.
SI-7852 Test to show status quo of for SomeModule.==

For which we can also elide the null check, and will in the
next commit.
SI-7848 Xlint says what looks interpolated

The motivating use case was an Expecty debug string
getting flagged for `$eq`.

The test case demonstrates a different bug, in which
the position of the literal tree is changed when typer
gets rid of the unused local, so that when the tree is
re-typed in erasure, a second, spurious warning is
emitted at the start of the method. Specifically, the
second warning is not suppressed because of the
different position.
SI-7852 Omit null check for SomeModule.==

For the same reasons outlined in the previous commits.
SI-7852 Refactor null-elision tests to be more focussed

 - Directly count null checks, rather than diffing the textual
   bytecode of the entire method
 - Add a test to show that the LHS needs to be a direct module
   reference, not just a tree with a module type, to elide the
   null check.
add syntactic extractor for assignment-like trees

There are three kinds of assign-like trees:

1. Assign(lhs, rhs)                          // $lhs = $rhs
3. AssignOrNamedArg(lhs, rhs)                // $lhs = $rhs
2. Apply(Select(f, nme.update), args :+ rhs) // $f(..$args) = $rhs

New syntactic combinator unifies all of them and lets users not to think
about these implementations details.
SI-7855 No missing interpolator warning post-typer

Avoid extra work, extra warnings.
SI-7848 Xlint no warn on $sym with params

This idea brought to you by retronym.
Require Ant >= 1.8.2

Reportedly our build fails with Ant earlier incarnations.
Time to raise the bar.

Tested by temporarily setting the requirement to 1.8.5 and observing:

    % ant init
    Buildfile: /Users/jason/code/scala/build.xml

    desired.jars.uptodate:

    boot:

    init:

    BUILD FAILED
    /Users/jason/code/scala/build.xml:216: Ant version 1.8.5 is required. You are running Apache Ant(TM) version 1.8.4 compiled on May 22 2012
Convenience methods from Try[T] => {Future, Promise}[T]
Upgrade: starr=M5, partest=RC5, xml=RC4, parsers=RC2.
add test case for SI-6719

The bug itself was fixed earlier in 95fe19545d60ae9aa79d2c8d5665c7f3b0cbdb1a

It was caused by improper wrapping of blocks in the toolbox's parse method.
Follow good interrupt discipline in Response

Restores the interrupted status of the waiting thread after catching
an InterruptException.
SI-7862: MANIFEST.MF file for Scala sources

In order to be able to use published Scala jars as OSGi bundles in the
Eclipse build, Eclipse needs to match sources and binaries. That is
done by making source jars *source bundles*. This PR adds the required
manifest entries. Nothing else should be affected (file names remain
the same).
SI-7725 - Vector concatenation is unreasonably slow

Rewrote ++ to use append or prepend when adding small collections to the end
or beginning of vectors.  This solves the extra-O(n) problem for addition of
single elements reported in SI_7725.

Renamed LgConcatFaster to Log2ConcatFaster (more widely recognizable).
Merge pull request #2967 from densh/topic/si-6719

Add test case for SI-6719
Merge pull request #2970 from dragos/improvement/source-osgi-headers

Fix SI-7862: MANIFEST.MF file for Scala sources
Merge pull request #2964 from retronym/topic/ant-18

Require Ant >= 1.8.2